Skip to main content
Glama

Tapetide - Indian Stock Market MCP

List Company Documents

list_company_documents
Read-onlyIdempotent

Index of a company's filings parsed to text (concall transcripts, annual reports, presentations, IPO documents): doc_id, type, period, date, num_pages, flags, and per-document links (raw PDF, full Markdown, summary Markdown). No prose. The doc_id is the input get_document_summary and read_document take; the links let the user open or download the document. Newest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_company_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax 50.
sinceNoOnly filings on/after YYYY-MM-DD.
symbolNoREQUIRED. Stock symbol, e.g. "RELIANCE".
tickerNoAlias for `symbol`.
doc_typesNoRestrict to these types (default all).
identifierNoAlias for `symbol`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Max 50."
    • removedInput schema / properties / limit / maximum
      Removed value: -50
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"number"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond that: the response is metadata only with 'No prose', it is sorted newest first, and it carries per-document raw PDF / Markdown / summary links — all things the annotations do not convey.

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 tightly packed sentences with no filler: what the index contains, what the doc_id enables downstream, and the sort order. Information is front-loaded and the terse 'No prose.' line efficiently rules out a common misreading.

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?

With no output schema, describing the returned fields and their purpose is exactly what this definition needed, and it does so. The remaining gap is minor: the schema marks symbol as REQUIRED while the definition reports zero required parameters and offers ticker/identifier aliases, and the description never explains that alias flexibility or the default type set.

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%, so every input parameter (limit, since, symbol, ticker, identifier, doc_types) is already documented in the schema, making 3 the baseline. The description's field list describes returned columns rather than adding meaning to the inputs, and it does not clarify the symbol/ticker/identifier alias relationship or the limit cap.

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?

The description states precisely what the tool returns: an index of a company's filings parsed to text, with the exact fields (doc_id, type, period, date, num_pages, flags, links) and the ordering (newest first). It also distinguishes itself from siblings by naming get_document_summary and read_document as consumers of the doc_id, so an agent can tell a listing call from a content call.

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?

Usage is clearly implied and partly explicit: this is the discovery step whose doc_id feeds get_document_summary and read_document, and the links are for opening/downloading rather than reading prose. It stops short of an explicit 'use this when you need to find a document, not when you already have a doc_id' statement, so it is not a full when/when-not treatment.

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.