Skip to main content
Glama
Sign In

P0 Agent Economy Index

by dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank
OverviewDiscussionsAdmin

SEC filings batch

sec_filings_batch
Read-onlyIdempotent

Use when you need recent SEC EDGAR filings for several US public companies at once: up to 10 tickers or CIKs in one POST. Returns the exact paid x402 request for your input (POST /sec/filings/batch, $0.03 per call), with the response schema and an example; POST that JSON body to the URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For one company use sec_filings. With a P0 access key (header Authorization: Bearer p0k_…, buy one at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/keys/buy?usd=5) this tool makes the paid call itself and returns the data, deducting the listed price.

Input Schema

NameRequiredDescriptionDefault
formNooptional, for every company: comma list of form types, e.g. 10-K,10-Q,8-K
factsNooptional, for every company: 0 = filings only (no XBRL facts; works for big banks too), default 1
limitNooptional, for every company: max filings returned (all requested forms together, newest first), as in the single call
sinceNooptional, for every company: only filings filed on/after this date, YYYY-MM-DD
companiesYes1 to 10 tickers or CIKs; duplicates are removed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"optional, for every company: filings per form, as in the single call"New value: +"optional, for every company: max filings returned (all requested forms together, newest first), as in the single call"
  2. Changed2 schema fields changed
    • addedInput schema / properties / facts
      Added value: +{
+  "description": "optional, for every company: 0 = filings only (no XBRL facts; works for big banks too), default 1",
+  "type": [
+    "string",
+    "integer"
+  ]
+}
    • addedInput schema / properties / since
      Added value: +{
+  "description": "optional, for every company: only filings filed on/after this date, YYYY-MM-DD",
+  "maxLength": 10,
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / companies / description
      Previous value: -"1 to 10 ticker or CIKs; duplicates are removed"New value: +"1 to 10 tickers or CIKs; duplicates are removed"
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent safety, yet the description discloses the non-obvious behavior that matters most: by default the tool returns a payable x402 request envelope (endpoint, price, response schema, example) rather than the filings themselves, and only with a P0 Bearer key does it execute the paid call. Pricing ($0.03/call) and pre-charge validation are stated. It stops short of describing pagination or how the response envelope should be interpreted step by step.

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-loaded with the use case and scope, then the return contract, then the key option — a sensible order with little waste. The inline key-purchase URL with a long hostname is visually noisy, though it is genuinely needed information.

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

Completeness5/5

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

A dual-mode tool (request-envelope vs self-executing with a key) with no output schema; the description covers both modes, the cost, the auth header form, and the input bound. An agent has everything needed to decide and invoke correctly.

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 every parameter (form, facts, limit, since, companies) is already documented and the description adds nothing beyond "up to 10 tickers or CIKs," which the schema also carries. Baseline 3 applies when the schema does the heavy lifting.

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 (recent SEC EDGAR filings for US public companies), the batching scope (up to 10 tickers or CIKs in one POST), and explicitly names the single-company sibling sec_filings. The distinction is legible without opening either schema.

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

Usage Guidelines5/5

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

"Use when you need... several US public companies at once" gives the positive trigger, and "For one company use sec_filings" gives the alternative and the condition that selects it. It also warns that invalid input is refused before any charge, so the agent knows retries are free.

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

All P0 Agent Economy Index toolsInspect
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