Macro-event and sector impact intelligence for Indian financial markets. Structured analysis of how policy, economic, weather, and geopolitical events affect Indian market sectors.
Single tool 'analyze_news' has a reasonable description (106 chars, within 10-1024 range) but critical schema gaps. Input schema visible with 'headline' (string, described) and 'published_at' (string, optional, described), but NO output schema documented. No error handling guidance, no recovery paths, no parameter constraints (e.g., headline length, timestamp format). Tool description mentions 'API key configuration' but does not explain how to provide it or what happens on auth failure. No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Naming 'analyze_news' is acceptable (verb_noun) but generic, does not convey 'Indian market' or 'sector impact' specificity. Parameter descriptions are minimal (7-30 chars each) and lack format/constraint details.
Analyze one Indian financial headline with Indian Market Intelligence for Macro Event & Sector Impact Analysis and return sector_vector for sector impact analysis. Requires API key configuration.
No output schema documented. LLM cannot infer what fields to expect (sector_vector structure, format, type). Breaks downstream tool chaining and forces LLM to guess at response shape.
Input parameters lack format/constraint details. 'headline' has no length bounds; 'published_at' has no timestamp format specified (ISO 8601? Unix epoch?). Invites invalid LLM input.
No error handling guidance. Description mentions 'Requires API key configuration' but does not explain failure modes (missing key, invalid key, rate limit, network error) or recovery steps.
No tool annotations. Tool is READ_ONLY (per metadata) but lacks readOnlyHint in schema. Idempotency not declared. Annotations help LLM reason about retry safety and side effects.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2026-07-28+ | v2 |
API key handling not documented. Description says 'Requires API key configuration' but does not specify: environment variable name, how to set it, what happens if missing, or whether it's injected server-side.