Conduit — Filings & Fundamentals

Get Quarterly Trend

get_quarterly_trend

Read-only

Quarterly trend for a key metric (revenue, net_income, eps_diluted, ...) from 10-Q filings.

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_quarterly_trend"
  }
}

Input Schema

Name	Required	Description	Default
`metric`	No	One of: revenue, gross_profit, operating_income, net_income, eps_diluted, total_assets, total_liabilities, total_equity, cash, long_term_debt, operating_cash_flow, capex	revenue
`ticker`	Yes	Stock ticker, e.g. AAPL
`periods`	No	Quarters to return (default 8, max 40)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety and scope are covered structurally. The description adds useful provenance (data comes from 10-Q filings), but says nothing about return ordering, fiscal-quarter labeling, or how missing quarters are handled.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the resource and scope lead. It is efficiently sized, though the terse phrasing borders on under-specification rather than being a model of clarity.

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

Completeness3/5

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

For a simple read-only tool with 100% schema coverage and no output schema, the definition is adequate but thin: it never indicates the shape of the returned trend series (quarter labels plus values) or the ordering, which an agent would want since no output schema exists to fall back on.

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 description coverage is 100%, with the metric enum-like list, ticker format, and periods default/max all documented in the schema. The description's metric examples merely restate what the schema already provides, so the baseline 3 applies.

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 retrieval ('quarterly trend for a key metric') plus the data source ('from 10-Q filings'), which implicitly separates it from annual-oriented siblings like get_annual_growth and from raw-fact tools like get_10q_facts. It does not explicitly name any alternative, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of which sibling to pick for related needs (e.g. annual trends, full statements, or peer comparison). The only hint is the '10-Q filings' source phrase, which is implied rather than stated as a selection criterion.

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?