This is a STDIO-only proxy bridge with no visible tool definitions in the source code. The three tools (get_transits, get_kundli_match, get_numerology) are mentioned only in smoke.mjs test file, not in actual tool registration code. The bridge forwards all JSON-RPC frames verbatim without parsing, validating, or documenting schemas. No input schemas are visible for any tool. Descriptions are minimal (10-30 chars). The server deliberately avoids knowing about tool payloads, making it impossible to assess definition quality. Since tool definitions are inferred rather than explicitly registered in code, per-tool scores are capped at 50.

• Add explicit tool registration with full JSON Schema input definitions. Each parameter must have type, description, and constraints (enum, min/max, pattern).
• Expand tool descriptions to 50-200 characters. Include: what the tool does, when to call it instead of similar tools, and what data it returns.
• Document output schemas for each tool. Specify field names, types, and what data the LLM should expect to extract.
• Add parameter descriptions explaining format, range, and valid values. E.g., 'date (ISO 8601 format, e.g. 2024-01-15)' instead of bare 'date'.
• Consider wrapping the proxy in a typed MCP server layer that validates and documents the upstream tool contracts, rather than forwarding frames blindly.