Skip to main content
Glama

Research data (x402)

filings_company

$0.002 via x402: A company by ticker or CIK: name, CIK, SIC and industry, state, fiscal year end, exchanges, former names, and its 10 latest filings with document links. Pay 0.002 USDC through https://store.agentexchange.work/gw/filings/company?ticker=AAPL Via the Agent Exchange store gateway; settled by Coinbase.

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

Input Schema

NameRequiredDescriptionDefault
cikNocik
tickerNoUS ticker (AAPL) or cik=<number>
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

B3.3/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 it discloses meaningful behavior: this is a paid x402 call costing 0.002 USDC, routed through the Agent Exchange gateway and settled by Coinbase, with the pricing/payment flow spelled out. It does not cover rate limits, failure modes, or refund behavior, but the payment mechanic is exactly the non-obvious context an agent needs before invoking.

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

Conciseness3/5

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

The core sentence is efficient, but it is preceded by a bare '$0.002 via x402' fragment and followed by a long, fully-qualified payment URL plus gateway/settlement boilerplate. The price is restated twice, and the front-loading leads with pricing rather than the resource.

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?

With no output schema, the description helpfully enumerates the returned fields, covering the main completeness gap for a lookup tool. However it omits anything about the optional x_payment flow when the payload is absent (beyond the schema note) and says nothing about errors or token/credit handling.

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%, so cik, ticker, and x_payment are already documented by the schema. The description restates 'ticker or CIK' but adds no formatting or precedence rules beyond what the schema provides. 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?

The description states a concrete resource (a company by ticker or CIK) and enumerates the fields returned (name, CIK, SIC, industry, state, fiscal year end, exchanges, former names, plus 10 latest filings). The purpose is clear without opening the schema. It does not explicitly differentiate itself from siblings filings_facts, filings_filings, or filings_search, which is the only gap.

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?

It says the tool takes a ticker or CIK but never states when to pick it over filings_facts, filings_filings, or filings_search. There are no exclusions, prerequisites, or alternative-routing guidance of any kind.

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