Skip to main content
Glama

SEC XBRL Frames Payment Quote

sec_xbrl_frames_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/sec/xbrl-frames (base $0.02; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?concept=Revenues&period=CY2024 (optional taxonomy, unit, limit 1-500, offset, order=desc|asc). XBRL frames: one XBRL concept for one calendar period, with one value per company that reported it (latest filed fact closest to the period, standard taxonomies only), sorted by value, with CIK, company, period end and accession number. Values are as reported by each company and may later be amended; reporting periods may not match the calendar exactly. USDC on Base only. Bad input: Not charged. Data from SEC EDGAR; not affiliated with or endorsed by the SEC. Not investment advice.

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": "sec_xbrl_frames_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: base price, USDC on Base only, no execution or payment by this tool, no charge on bad input, payment via 402/x402, SEC EDGAR provenance, amendment risk, and calendar-period mismatch caveats.

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?

Front-loads the core payment-terms purpose, URL, price, and quote-only behavior, then moves to payment procedure and caveats. It is slightly repetitive, especially 'USDC on Base only' appearing twice, but no major sentence is wasted.

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?

No output schema exists, and the description covers price, currency, network, payment protocol, data source, and relevant caveats. It could more explicitly describe the shape of the returned payment terms, but it is largely complete for a quote tool.

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?

The tool input schema has zero parameters, so the baseline is 4. The description documents query parameters for the underlying HTTP endpoint, which is useful context but not tool invocation parameters.

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?

States a specific verb and resource: returns payment terms for the SEC XBRL frames endpoint. It explicitly says the tool never runs the check or pays, which distinguishes it from an execution or data-fetch operation.

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

Usage Guidelines4/5

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

Gives clear context that this is quote-only and that payment happens over HTTP with x402 v2. It does not explicitly compare when to use this versus sibling quote tools such as http or sec_company_facts, but the quote-only workflow is clear.

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.