Skip to main content
Glama
screener-mcp
by LogeshR15

get_document_list

Read-only

List a company's available annual reports and earnings call transcripts by NSE/BSE symbol, showing which years and quarters can be searched in company research.

Instructions

List all available annual reports and earnings call transcripts for a company.

Fetches from Screener.in company page and NSE API.

symbol: NSE/BSE symbol (e.g., "TCS", "INFY")

Use this to see which years/quarters ask_company_research can search. Annual reports are de-duplicated per year (a PDF is preferred over a .zip).

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": {
      "symbol": "<symbol>"
    },
    "name": "get_document_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile and external-network reach are covered. The description adds genuinely non-obvious behavior: two distinct upstream sources (Screener.in and NSE) and a de-duplication rule stating a PDF is preferred over a .zip per year. It omits failure behavior for invalid symbols or partial-source failures, which keeps it short of a 5.

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 lines, front-loaded with the purpose and followed by sources, parameter format, and the intended use. The standalone "symbol:" line is slightly redundant with the schema's required property name, but it earns its place by supplying format and examples that the schema lacks.

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 single-parameter read-only listing tool with an output schema, an agent needs purpose, symbol format, sources, and what the result inventory means. All four are present, and the output schema relieves the description of explaining return structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter has no description in the schema, so the description must carry the burden — and it does, defining symbol as an NSE/BSE ticker with concrete examples ("TCS", "INFY"). That is exactly the missing meaning an agent needs to construct a valid call.

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 first sentence names a specific verb (List), a specific resource (annual reports and earnings call transcripts), and a scope (for a company). It also names the upstream sources (Screener.in, NSE API), which makes the tool's role as a document-inventory endpoint distinct from siblings like ask_company_research or get_financials.

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?

"Use this to see which years/quarters ask_company_research can search" gives a clear when-to-use condition and names the downstream consumer, effectively positioning it as a precursor step. It stops short of stating when-not to call it (e.g., if you only need financials, skip this and use get_financials), so there is no explicit exclusion.

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