Skip to main content
Glama
Sign In

Fivebar Trading

by io.github.fivebar-xyz
OverviewDiscussionsAdmin

Search every SEC filing (EDGAR full text)

filing_search
Read-only

EDGAR's full-text search across every SEC filing since 2001: which filings mention a phrase, by whom, when. Filter by form (10-K, 8-K, S-1, DEF 14A...), company and dates. Use quotes for an exact phrase ('"going concern"'), OR between alternatives. Returns the total, the top filers, and the matching documents with links. A match only means the words appear; read the passage with filing_text before saying what a filing says.

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": {
      "query": "<query>"
    },
    "name": "filing_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date YYYY-MM-DD (default today)
fromNoStart date YYYY-MM-DD (default one year ago)
formsNoComma-separated forms, e.g. 10-K,10-Q
limitNoDocuments to list, default 10, max 25
queryYesWords or a "quoted phrase"
companyNoOnly this company's filings (ticker, name or CIK)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower, and the description still adds genuine context: it discloses the return shape (total, top filers, matching documents with links) and a critical semantic caveat that a match only means the words appear. It stops short of discussing rate limits, pagination beyond the limit cap, or coverage gaps in EDGAR's text corpus.

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

Conciseness5/5

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

Three dense sentences, front-loaded with what the tool searches and over what scope, then syntax, then output shape, then the caution. No filler and every clause carries information an agent needs.

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?

No output schema exists, yet the description characterizes the return value and flags the main misinterpretation risk for this tool. With 6 parameters fully documented in schema and one required query, nothing material is missing for correct invocation.

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?

Schema coverage is 100%, so a 3 is the baseline, but the description adds real meaning beyond the schema by explaining query operators (quoted phrases, OR) and enumerating form values such as 10-K, 8-K, S-1 and DEF 14A. It does not discuss the from/to defaults or the limit ceiling, which are only in the schema.

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 — EDGAR full-text search across every SEC filing since 2001 — plus the scope of what it answers ('which filings mention a phrase, by whom, when'). An agent can distinguish this from filing_text, which reads passages rather than finding them.

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?

Gives explicit query syntax rules (quotes for exact phrase, OR between alternatives) and names the sibling to use for the next step ('read the passage with filing_text before saying what a filing says'). It also implicitly carves out filtering by form, company and dates, so both how-to-use and when-to-use are covered.

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

All Fivebar Trading 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