get_comparative_source_state — schedule iii MCP Tool Read-only
get_comparative_source_state
(get comparative source state) is one of 67 tools on the
schedule iii
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_comparative_source_state from your client
- Claude Code schedule iii get_comparative_source_state run in your project directory
- Claude Desktop schedule iii get_comparative_source_state ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor schedule iii get_comparative_source_state ~/.cursor/mcp.json
- VS Code schedule iii get_comparative_source_state .vscode/mcp.json
- Zed schedule iii get_comparative_source_state ~/.config/zed/settings.json
- Windsurf schedule iii get_comparative_source_state ~/.codeium/windsurf/mcp_config.json
- Cline schedule iii get_comparative_source_state ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI schedule iii get_comparative_source_state ~/.gemini/settings.json
- Grok schedule iii get_comparative_source_state .mcp.json (in your project root)
- ChatGPT schedule iii get_comparative_source_state Settings → Connectors → Advanced → Developer mode
- Claude.ai schedule iii get_comparative_source_state Settings → Connectors → Add custom connector
- LangChain schedule iii get_comparative_source_state pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http schedule-iii https://app.datavrn.com/api/mcpOther tools on this server
- list_clients
- create_client
- upload_trial_balance
- get_upload
- set_header_row
- confirm_column_mapping
- ingest_upload
- list_periods
- get_schedule3_workspace
- list_grouping_suggestions
- confirm_groupings
- save_adjustments
- save_py_values
- save_asset_movements
- save_provision_movements
- save_reserves_movements
- save_share_capital
- save_statement_settings
- save_disclosures
- declare_capture_na
- confirm_capture_review
- revoke_capture_declaration
- copy_capture_declarations
- save_partner_capital
- get_partner_capital
- save_accounting_policies
- save_regulatory_affirmations
- list_statement_policy_choices
- get_finalise_readiness
- finalise_statement
- assert_previous_year_no_activity
- generate_schedule_iii
- get_job
- list_snapshots
- get_workbook_download
- create_upload_link
- get_upload_link_status
- get_statement_figures
- get_statement_notes
- get_tb_rows
- get_pending_work
- list_allocation_runs
- get_allocation_account_figures
- get_allocation_target_figures
- get_spreading_reconciliation
- list_budgets
- get_budget
- get_variance_report
- get_consolidated_statements
- list_cost_centres
- create_cost_centre
- list_profit_centres
- create_profit_centre
- list_account_mappings
- confirm_centre_mappings
- list_reporting_lines
- confirm_reporting_lines
- get_setup_status
- list_replacements
- preview_replacement_restore
- restore_replacement
- list_chart_rebaselines
- preview_chart_rebaseline
- confirm_complete_chart
- verify_connection
- get_help
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.