Catalog of curated market-wide analyses with parameters. FREE. Call before market_insight / buffett_* to see options.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description mentions it is 'FREE' but lacks other behavioral details (e.g., rate limits, caching). Since it is a simple read-only tool with no annotations, minimal disclosure is acceptable.
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?
Two front-loaded sentences with no wasted words, conveying purpose, cost, and usage guidance efficiently.
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?
Tool is simple; description covers purpose and usage context. Output schema exists, so return format details are not required. Slightly incomplete: does not explicitly state what the catalog returns, but sufficient for the tool's simplicity.
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?
Tool has no parameters, input schema coverage is 100%, and description does not need to add parameter details; baseline of 4 is appropriate.
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?
Description clearly states it is a 'catalog of curated market-wide analyses' and instructs to call before specific sibling tools (market_insight, buffett_*), making the tool's purpose and differentiation evident.
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?
Explicitly says 'Call before market_insight / buffett_* to see options,' providing direct when-to-use guidance relative to alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct purpose: quality scoring, valuation, raw facts, filings, financials, peer comparison, industry aggregates, insider activity, institutional ownership, market insights, screening, short pressure, and standard scores. No overlaps in functionality.
All tools use consistent snake_case naming with descriptive prefixes (e.g., company_, buffett_, market_). The pattern is predictable and helps infer tool purpose.
14 tools cover a broad range of SEC fundamentals without being overwhelming. Each tool serves a clear role, and the count is appropriate for a comprehensive financial data API.
Covers core areas: filings, financials, insider trades, institutional ownership, screening, scores, and market insights. Minor gaps (e.g., no direct analyst estimates or corporate events) but overall very well-scoped for the domain.