Conduit — Filings & Fundamentals

Get Peer Comparison

get_peer_comparison

Read-only

Rank a company against ALL SEC filers for one metric and calendar period (frames API). Uses the company's own current XBRL tag unless overridden.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "get_peer_comparison"
  }
}

Input Schema

Name	Required	Description	Default
`tag`	No	Explicit XBRL tag override, e.g. Revenues
`unit`	No	Unit, e.g. USD (default USD)	USD
`metric`	No	Metric to rank (revenue, gross_profit, operating_income, net_income, eps_diluted, total_assets, total_liabilities, total_equity, cash, long_term_debt, operating_cash_flow, capex); default revenue	revenue
`period`	No	CY2024 or CY2024Q4; omit for latest available year
`ticker`	Yes	Stock ticker, e.g. AAPL
`taxonomy`	No	XBRL taxonomy (default us-gaap)	us-gaap

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context that it uses the frames API and defaults to the company's own current XBRL tag unless overridden, but says nothing about the shape or comparability of the ranked result.

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

Conciseness5/5

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

Two tight sentences, front-loaded with the core action and scope, with no filler. Every clause (frames API, default tag) carries information.

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

Completeness4/5

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

With readOnly annotations covering safety, fully documented params, and no output schema requiring explanation, the description is nearly self-sufficient. It could be stronger by contrasting with compare_companies, but nothing essential for a correct call is missing.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all six parameters, establishing a baseline of 3. The description adds a modest value by clarifying the default tag behavior ('company's own current XBRL tag unless overridden'), which the schema's tag field does not state, but adds no other parameter detail.

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

Purpose4/5

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

States a specific verb (Rank) plus resource (a company against ALL SEC filers) and the mechanism (frames API) for one metric and period. It is clear what the tool does, but it never names its closest sibling compare_companies, so the agent must infer the distinction.

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

Usage Guidelines3/5

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

The description implies the use case (cross-filer ranking for a single metric/period via the frames API) but offers no explicit when-to-use vs when-not, and does not route the agent to compare_companies for multi-company comparisons. The 'unless overridden' clause hints at default behavior but is not framed as guidance.

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

All Conduit — Filings & Fundamentals tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?