SignalFuse MCP Server

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

No annotations are provided, so the description carries full disclosure burden. It adds the behavioral trait 'fused' (describing signal type), but omits safety profile (read-only status), error behavior for invalid symbols, rate limits, or return format.

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 sentences with zero waste: first states purpose, second provides usage syntax. Front-loaded structure with no filler text.

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?

Adequate for a simple 2-parameter read tool, but lacks description of return values (no output schema exists to compensate). The 'fused' concept is mentioned but not elaborated.

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?

With 100% schema description coverage, the baseline is 3. The description reinforces the symbols parameter syntax but adds no additional semantic context beyond what the schema provides for either 'symbols' or 'credit_token'.

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 uses specific verb 'Get' with resource 'fused signals' and scope 'multiple assets at once'. The phrase 'multiple assets at once' clearly distinguishes this from sibling tool 'get_signal' (implied singular), establishing this as the batch variant.

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 implies batch usage through 'multiple assets at once' and provides syntax guidance ('Pass comma-separated symbols or omit for all'), but does not explicitly state when to use this versus 'get_signal' or mention the credit_token use case.

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