Skip to main content
Glama

Agent Exchange store

filings_facts

$0.005 via x402: An XBRL financial concept as a time series for a company (us-gaap, e.g. Revenues, NetIncomeLoss, Assets, EarningsPerShareDiluted, CommonStockSharesOutstanding): the last 16 reported periods with value, period, fiscal year and quarter, form and filing date; or, without a concept, the list of available concepts. Pay 0.005 USDC through https://store.agentexchange.work/gw/filings/facts?ticker=MSFT&con

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "filings_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNocik
tickerNoUS ticker (AAPL) or cik=<number>
conceptNous-gaap concept name; omitted: the concept list
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the price ($0.005 USDC via x402), the payment gateway URL, that omitting payment returns the price, and the return shape (last 16 periods with value, period, FY, quarter, form, filing date). It omits rate limits and error/edge behavior, keeping it short of a 5.

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?

It is a single dense sentence with cost front-loaded, which suits a paid tool, and every clause adds information. The embedded payment URL and the truncated tail ('&con') slightly hurt readability.

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?

For a paid data endpoint with no output schema and no annotations, the description covers return fields, the concept/non-concept branch, and the payment flow. It could still say more about period coverage limits or failure modes, but the essentials are present.

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

Parameters4/5

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

Schema coverage is 100%, so a 3 is the baseline, but the description adds value beyond the schema by giving real concept-name examples and clarifying the concept-omitted behavior. ticker/cik and x_payment are already well described in the schema, so the gain is modest.

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

Purpose5/5

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

The description names a specific resource (an XBRL financial concept as a time series for a company) and enumerates concrete us-gaap examples (Revenues, NetIncomeLoss, Assets, EPS, SharesOutstanding). It also discloses the dual mode — concept present returns the last 16 periods, concept omitted returns the concept list — so an agent knows exactly what it produces.

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?

It gives a toggling rule for the concept parameter (with concept -> time series; without -> concept list) and explains the x402 payment path, but offers no explicit when-to-use-this-vs-siblings guidance relative to filings_company, filings_filings, or filings_search.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources