query_vimshottari_date — Sahadeva MCP Tool Read-only
query_vimshottari_date
(query vimshottari date) is one of 98 tools on the
Sahadeva
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call query_vimshottari_date from your client
- Claude Code Sahadeva query_vimshottari_date run in your project directory
- Claude Desktop Sahadeva query_vimshottari_date ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Sahadeva query_vimshottari_date ~/.cursor/mcp.json
- VS Code Sahadeva query_vimshottari_date .vscode/mcp.json
- Zed Sahadeva query_vimshottari_date ~/.config/zed/settings.json
- Windsurf Sahadeva query_vimshottari_date ~/.codeium/windsurf/mcp_config.json
- Cline Sahadeva query_vimshottari_date ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Sahadeva query_vimshottari_date ~/.gemini/settings.json
- Grok Sahadeva query_vimshottari_date .mcp.json (in your project root)
- ChatGPT Sahadeva query_vimshottari_date Settings → Connectors → Advanced → Developer mode
- Claude.ai Sahadeva query_vimshottari_date Settings → Connectors → Add custom connector
- LangChain Sahadeva query_vimshottari_date pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sahadeva https://sahadeva.magicteams.ai/mcpOther tools on this server
- recommend_tools
- search_locations
- calculate_chart_from_known_place
- compare_family_timing
- calculate_compatibility
- calculate_relationship_compatibility
- get_panchanga
- find_muhurta
- find_elected_lagna
- calculate_doshas
- calculate_kp
- calculate_jaimini
- calculate_varshaphal
- calculate_ayanamsa_chart
- detect_life_themes
- consult_jyotishya
- analyze_chart_topic
- validate_rule_spec
- reconstruct_worked_example
- compare_conventions
- analyze_house
- prepare_consultation_intake
- build_prediction_journal
- get_planetary_relationship_graph
- get_natal_panchanga
- calculate_crystal_profile
- analyze_sibling_bond
- get_book_rule_findings
- analyze_lal_kitab
- explore_lal_kitab_sources
- analyze_lal_kitab_remedies
- reason_lal_kitab
- explore_lal_kitab_remedy_catalog
- get_remedy_catalog
- suggest_safe_practice
- calculate_devata_profile
- analyze_remedies
- build_remedy_repertoire
- analyze_transit_activation
- calculate_strength_profile
- calculate_ashtakavarga
- analyze_varga
- analyze_yogas
- analyze_special_points
- analyze_transits
- calculate_dasha_system
- analyze_badhaka
- analyze_arudha_and_upapada
- audit_reading_evidence
- explain_chart_sources
- compare_reading_versions
- analyze_nakshatra_profile
- analyze_marriage_structure
- analyze_career_structure
- analyze_education_structure
- analyze_property_and_vehicle
- analyze_finance_structure
- analyze_spiritual_path
- build_claim_evidence_ledger
- analyze_name
- find_muhurta_with_natal_fit
- run_longitudinal_validation
- generate_full_life_report
- get_full_reading_context
- get_full_life_report_section
- calculate_south_indian_chart
- describe_methodology
- calculate_gochara
- calculate_gochara_from_known_place
- calculate_ingress_timeline
- simulate_birth_time_uncertainty
- knowledge_status
- get_rule_hit_rates
- assess_prediction_readiness
- audit_chart_calculation
- list_rule_review_queue
- get_rule_citations
- get_synthesis_validation_status
- get_compact_chart_evidence
- get_timing_context
- build_slow_transit_calendar
- find_marriage_windows
- get_marriage_readiness
- render_chart
- generate_report_pdf
- calculate_prashna
- record_prashna_outcome
- get_depth_analysis
- fuse_timing
- rectify_birth_time
- search_reviewed_rules
- search_source_passages
- compare_traditions
- audit_prediction_claim
- record_consultation_outcome
- get_validation_report
- review_lal_kitab_rule
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 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.