Crypto, web, finance and app data tools

SEC Full-Text Search

sec_full_text_search

Search the full text of all SEC filings since 2001 for any word or exact phrase (in quotes), filtered by form type (10-K, 8-K, S-1...) and date: company, form, filing date, period and document link. Use to find every filing mentioning a risk, product, customer or event.

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": {
      "q": "<q>"
    },
    "name": "sec_full_text_search"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes
`end`	No
`forms`	No
`limit`	No
`start`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations exist, so the description must carry the behavioral burden. It discloses coverage (since 2001) and phrase syntax, but says nothing about result ranking, pagination (the limit param exists), rate limits, or that the search is a read-only operation. Useful context, but incomplete for a no-annotation tool.

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?

Two dense sentences that front-load the core capability and follow with usage. The output-field list ('company, form, filing date, period and document link') is slightly run-on but earns its place by describing returns. Minimal waste.

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?

An output schema exists, so return values needn't be described, and coverage/scope is stated. But with five params at 0% schema coverage, the omission of start/end/limit semantics leaves the definition short of what an agent needs to invoke it precisely.

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 coverage is 0%, so the description must document all five params, and it only partially does: it explains the query (word or quoted phrase) and form types (10-K, 8-K, S-1), and gestures at date filtering. It never names start/end explicitly or explains limit, leaving gaps the schema cannot fill.

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 uses a specific verb (search) on a specific resource (full text of all SEC filings since 2001) and defines scope (coverage start date, phrase-in-quotes syntax). It distinguishes the full-text capability implicitly, but never names a sibling like us_company_filings or sec_metric_screen to route the agent, so it falls just below the top score.

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?

'Use to find every filing mentioning a risk, product, customer or event' gives a concrete use case with examples. There are no when-not conditions and no alternative tools cited, so it stops short of full differentiation.

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

All Crypto, web, finance and app data tools 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?