SALT19 Agent Utility Grid

Sec Recent Filings

sec-recent-filings

Idempotent

Return recent SEC EDGAR filings for a company CIK from the live SEC submissions feed, normalized for agent consumption. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility.

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": {
      "cik": "<cik>"
    },
    "name": "sec-recent-filings"
  }
}

Input Schema

Name	Required	Description
`cik`	Yes
`limit`	No
`_salt19_handoff_id`	No	Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry.
`_salt19_operation_id`	No	Optional but recommended semantic purchase identifier preserved across challenge/payment/retries.
`_x402_payment_signature`	No	Optional x402 payment proof. Omit on the first call; include after satisfying the challenge.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already provide idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds useful context about the live feed, normalization for agents, and the $0.01 x402 payment requirement. However, it does not explain the implications of readOnlyHint=false for a tool that ostensibly only returns data, nor the payment challenge flow.

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?

The description is short and front-loaded with the core purpose. The price and operation_id sentence are useful but partially duplicate the schema's own description of `_salt19_operation_id`, so the structure is good but not maximally tight.

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

Completeness2/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 should explain what shape the normalized filings take, but it only says 'normalized for agent consumption.' It also omits `limit` semantics and provides no differentiation from sec-company-facts. The price and source are helpful, but significant context an agent needs to invoke this correctly is missing.

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

Parameters2/5

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

Schema coverage is only 60%, and the two undocumented parameters include `limit`, which has no schema description and is not mentioned in the tool description. The description adds some semantic context for `cik` ('company CIK') and repeats the operation_id recommendation, but it does not compensate for the missing guidance on `limit`.

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 clearly states a specific action ('Return'), a specific resource ('recent SEC EDGAR filings for a company CIK'), and a source ('live SEC submissions feed'). It does not explicitly contrast with the sibling tool sec-company-facts, so it stops short of a full 5, but the resource type is specific enough for an agent to form an initial expectation.

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 guidance about when to choose this tool over sec-company-facts or other SEC-related tools. The description mentions price and an optional operation ID, but does not state conditions, exclusions, or alternatives.

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

All SALT19 Agent Utility Grid 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?