Skip to main content
Glama

Silicon Floor

by com.siliconfloor
OverviewDiscussionsAdmin

Recent SEC filings of a company

get_filings
Read-only

Returns a company's recent SEC filings, classified (earnings, 8-K items, notes and loans, share offerings, prospectuses…), each with its acceptance time, accession number and sec.gov link; a financing filing carries what it says — amount, coupon, maturity, status, the sentence it comes from. Insider filings (Forms 3, 4, 5 and 144) are left out unless asked for: their purchases and sales are summed over 90 days in insiderFlow90d, with the filer's role, not the person's name. Filings are dated by acceptance time, not filing date. Use it when the user asks what a company has filed, announced, borrowed or raised recently.

Input Schema

NameRequiredDescriptionDefault
limitNoFilings to return (default 15, max 50).
symbolYesTicker or company name, e.g. NVDA, AMD, ASML, 'nvidia', 'taiwan semiconductor'. Case-insensitive.
insidersNoInclude insider filings (Forms 3, 4, 5 and 144), left out by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / insiders
      Added value: +{
+  "description": "Include insider filings (Forms 3, 4, 5 and 144), left out by default.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With readOnly/destructive annotations already covering the safety profile, the description still adds real behavioral context: insiders are excluded unless requested, insider activity is aggregated over 90 days by filer role rather than name, and filings are dated by acceptance time rather than filing date. These are non-obvious semantics an agent could not infer from structured fields.

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 what is returned, then exclusions, then the usage trigger. Dense but every clause carries information; the trailing classification list ('amount, coupon, maturity, status, the sentence it comes from') is slightly verbose but still earns its place.

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 3-parameter read tool with no output schema, the description covers return content, the extra insiderFlow90d field, default exclusions and date semantics. It stops short of describing ordering of results or what happens when no filings exist, minor gaps given the strong coverage.

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 the baseline is 3; the description goes further by explaining the meaning of `insiders` (what gets included and how insiderFlow90d is computed) and the acceptance-time basis for ordering/limit. `limit` itself gets no extra detail beyond 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 ('Returns a company's recent SEC filings') plus the classification scheme and the fields each carries. It also distinguishes itself from insider-oriented siblings by explicitly scoping out Forms 3/4/5/144 by default.

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?

Ends with an explicit trigger: 'Use it when the user asks what a company has filed, announced, borrowed or raised recently.' It clarifies the insider opt-in condition, but does not name a sibling (e.g. get_insider_trading) as the alternative when the user wants insider data, so routing is implied rather than stated.

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

All Silicon Floor 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