Skip to main content
Glama
tearsheet

tearsheet

by kewonit

search_filings

Read-only

Search downloaded filings offline by PDF text or XBRL figure names, filter by company, and return file and page hits for opening with read_filing.

Instructions

Search the filings the user downloaded into their filings folder.

    Searches PDF text, such as annual reports and concall transcripts, and
    the figure names in XBRL results filings. company narrows to one
    company by NSE symbol, BSE code or name. Works offline. Returns the file
    and page of each hit, which read_filing can then open.
    

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
companyNo

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofNo
unitsNo
entityNo
sourcesNo
warningsNo
next_cursorNo
retrieved_atNo
verificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations supply only readOnlyHint=true, and the description adds real behavioral context beyond that: the corpus is limited to files the user already downloaded, it operates offline, and it returns file plus page coordinates rather than document text. It does not mention result-count behavior or the result cap, but the essential operating envelope is disclosed.

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?

Four short sentences, front-loaded with the core action, then scope, then the filter, then the return/workflow. Slightly redundant phrasing ('the filings ... into their filings folder') costs a little, but nothing is padding.

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?

For a three-parameter read-only search with an output schema present, the description covers corpus scope, offline behavior, filter semantics, and the downstream read_filing step. An agent has everything needed to call it correctly and reuse its results.

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 0%, so the description must carry parameter meaning. It does well for two of three: company is explained as an NSE symbol, BSE code, or name (far beyond the schema's bare anyOf string), and query is characterized as matching PDF text and XBRL figure names. limit is never mentioned, though its default and 1-30 bounds are visible 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 ('Search the filings the user downloaded into their filings folder') and sharpens it with the content types searched (PDF text such as annual reports and concall transcripts, plus XBRL figure names). It also distinguishes itself from the retrieval sibling by noting that hits are locations 'which read_filing can then open', so an agent can tell the two apart without opening a schema.

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?

Clear context for when this applies: only over locally downloaded filings, working offline, with company as the narrowing filter. The workflow handoff to read_filing after a hit is explicit. What's missing is any exclusion — it never says when to prefer search_screen_fields or the other search-like siblings instead.

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