finstack-mcp

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Discloses 'real-time' data freshness and enumerates specific return fields (price, change, volume, market cap, P/E, sector, country). Missing potential rate limits, caching behavior, or error conditions, but covers core behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with purpose first, then scope, returns, detailed args, and examples. Front-loaded with critical information. Minor verbosity in examples section (repetitive '→ [Company] live price' pattern), but overall efficient given the need to document complex symbol formats.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive for a single-parameter tool. Addresses global exchange complexity through detailed symbol format documentation. Acknowledges output schema existence by summarizing key return fields without over-documenting. References sibling tool for scope clarification. Complete given the tool's complexity and schema limitations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (symbol parameter has no description), but description compensates extensively with format specifications for US (.L), UK (.L), Japan (.T), Hong Kong (.HK), and India (.NS) exchanges, plus concrete examples. Fully documents the single parameter's syntax requirements beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Clear specific verb ('Get') + resource ('real-time stock quote') + scope ('any global stock'). Explicitly distinguishes from sibling nse_quote by stating 'use nse_quote for Indian stocks', clarifying this tool's broader global scope versus region-specific alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit alternative tool (nse_quote) for Indian stocks, establishing clear when-not-to-use guidance. However, lacks differentiation from other stock-related siblings like stock_historical or company_profile regarding when to prefer this over historical data or fundamental analysis.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.