Get the original SEC filing URL for a fiscal quarter or year from Rockmoon's stored provenance; use this instead of web search.
| Name | Required | Description | Default |
|---|---|---|---|
| period | No | ||
| ticker | Yes | ||
| frequency | No | auto | |
| statement | No | all |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as authentication requirements, rate limits, or error handling. The mention of 'Rockmoon's stored provenance' hints at source but lacks depth.
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?
The description is a single, front-loaded sentence with no redundancy. Every word serves a purpose.
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?
While an output schema exists, the description lacks parameter explanations and behavioral details for a tool with four parameters and no annotations. It is too minimal given the complexity.
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 description coverage is 0%, and the description does not explain any of the four parameters (ticker, period, frequency, statement). The agent must rely solely on parameter names, which is insufficient.
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?
The description clearly states the tool retrieves the original SEC filing URL for a fiscal quarter or year, and distinguishes it from web search. The verb 'Get' and the resource 'SEC filing URL' are specific.
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?
The description provides explicit guidance: 'use this instead of web search,' which tells agents when to prefer this tool. However, it does not mention when not to use it or address sibling tools, but the context is clear enough.
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 targets a distinct financial data aspect (e.g., balance sheet vs income statement vs cash flow; different holding types; metrics vs history). No overlapping purposes.
All tools follow verb_noun pattern with snake_case (e.g., get_balance_sheet, compare_metrics). Consistent and predictable.
19 tools is slightly above the typical 3-15 range but covers a broad domain (statements, metrics, holdings, screening). Still reasonable and well-scoped.
Covers most key financial data needs: statements, metrics, insider trades, institutional holdings, screen/search. Minor gaps like earnings estimates or dividend history are absent but core workflows are complete.
