Skip to main content
Glama
Sign In

Fivebar Trading

by io.github.fivebar-xyz
OverviewDiscussionsAdmin

What a filing says (SEC)

filing_text
Read-only

The text of a company's SEC filing, or one section of it: a 10-K's or 10-Q's risk factors, legal proceedings, management's discussion (MD&A), business or cybersecurity; what an 8-K announced (and its exhibits, like the EX-99.1 press release); a proxy's (DEF 14A) executive pay; an S-1. Pass a section by plain name ('risk factors', 'legal proceedings', 'MD&A') or item ('item 1a', 'item 2.02'), and/or a query to get just the passages that mention it ('going concern', 'customer concentration'). Defaults to the latest 10-K. Long sections come in pages (offset). Every result links to the document. Quote the filer's words.

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": {
      "company": "<company>"
    },
    "name": "filing_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
nthNo0 = latest filing of that form (default), 1 = the one before...
formNo10-K (default), 10-Q, 8-K, DEF 14A, S-1, 20-F, 6-K, 424B5...
queryNoWords to find; returns the passages around them
filingNoA specific filing: accession number or sec.gov link
offsetNoCharacter offset to continue a long section (nextOffset from the last call)
companyYesTicker, company name or SEC CIK
exhibitNoAn exhibit of the filing instead of its main document, e.g. 99.1 (an 8-K's press release)
sectionNoA section: 'risk factors', 'legal proceedings', 'MD&A', 'business', 'item 1a', 'item 2.02'...
max_charsNoDefault 8000, max 20000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely new behavior: long sections are paginated via offset, every result links back to the source document, and quoting is the intended use. It stops short of saying what a result object contains or how a missing/ambiguous filing behaves.

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 purpose, then param usage, then defaults and pagination — a sensible order. It is dense with parenthetical examples in a single paragraph, which borders on over-stuffing, but nearly every clause carries operational information.

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?

For a nine-parameter, no-output-schema tool, it covers defaults, section/query/exhibit addressing, and pagination, which is what an agent needs to call it correctly. The remaining gap is the shape of the returned text (full section vs. excerpts, and the link field), which is left implicit.

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 100%, so all nine parameters are already documented, which sets the baseline at 3. The description does add useful examples beyond the schema ('risk factors', 'item 1a', 'going concern', EX-99.1 press release) and clarifies the offset/nextOffset continuation pattern, but most of that meaning is already present in the field descriptions.

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 concrete verb and resource ('The text of a company's SEC filing, or one section of it') and enumerates the form types and section names it covers, so an agent knows exactly what comes back. It is clearly a text-retrieval tool rather than a search or metrics tool, which separates it from the surrounding catalog.

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 concrete operating guidance: default is the latest 10-K, section can be passed by plain name or item number, query narrows to matching passages, offset continues long sections. It does not explicitly route the agent to alternatives (e.g. filing_search for discovery, company_financials for computed numbers), leaving that to inference.

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