Skip to main content
Glama

FinanceQuery

SEC EDGAR Full-Text Search

get_edgar_search
Read-onlyIdempotent

Full-text search across SEC EDGAR filings with optional form type and date filters. Requires EDGAR_EMAIL env var.

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": "get_edgar_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoPagination offset; omitted = 0 (first page)
sizeNoPage size; omitted = 100, max 100
formsNoComma-separated form types to filter (e.g., "10-K,10-Q,8-K")
queryYesSearch query (keywords in filing text)
end_dateNoEnd date filter in YYYY-MM-DD format
start_dateNoStart date filter in YYYY-MM-DD format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds one genuinely useful behavioral fact not in annotations: it requires the EDGAR_EMAIL env var. It does not mention SEC rate limiting or what the result set looks like, so it adds some value but not rich context.

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?

Two short sentences with zero filler: capability and scoping first, then the prerequisite. Nothing is duplicated or wasted, and the critical information is front-loaded.

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?

For a 6-parameter search tool with no output schema, the description leaves the agent without any indication of what search results contain (filings, snippets, pagination metadata) and omits SEC rate-limit behavior, which matters for repeated paginated calls. The schema covers inputs fully, so the gap is moderate rather than severe.

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 description coverage is 100%, with every parameter (query, forms, start_date, end_date, from, size) documented in the schema itself. The description only echoes the form-type and date filters and adds no format details, syntax, or defaults beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource: 'Full-text search across SEC EDGAR filings' with 'optional form type and date filters'. An agent can immediately tell this is keyword search over filing text, distinct from retrieval-by-identifier tools like get_edgar_submissions or get_filing_sections, though the description does not name any sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the phrase 'full-text search' plus the optional filter list; there is no explicit statement of when to prefer this over section/fact retrieval tools, and no exclusions or prerequisites beyond the env var. An agent must infer the selection rule from the tool's scope.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.