Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Results Declared

get_results_declared
Read-onlyIdempotent

Companies that filed quarterly results in a time window, newest first. One row per company and quarter: filed_at (latest results filing, IST), declared_at (first original filing held, or null), revision, and revenue and net profit in INR crore as filed (basis consolidated when filed, else standalone; revenue is interest earned for banks, can be null). Answers "who reported today"; with symbols (up to 500) it checks a whole list in one call, so call get_financials only for the stocks that changed. If meta.has_more, repeat with since = meta.since and until = meta.next_until. NSE and BSE filings from August 2026 on.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows per call (default 50, max 50).
sinceNoWindow start, inclusive: YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS, IST. Default: start of yesterday.
untilNoWindow end, exclusive, same formats. Default: now.
symbolsNoOnly these stocks: NSE symbols or BSE scrip codes, e.g. ["VOLTAS","UPL"]. Omit for every company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is lower — yet the description still adds substantial context: sort order, row grain, `filed_at` in IST, `declared_at` nullable, `revision` semantics, consolidated-vs-standalone `basis` fallback, bank revenue as interest earned, and possible nulls. It also discloses the data coverage boundary ('NSE and BSE filings from August 2026 on'), which no annotation conveys.

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 purpose and grain, then fields, then the workflow/pagination tail — logical and information-dense with no filler sentences. It is slightly crowded by stacked parentheticals (basis rules, bank revenue, null caveats), which costs a little readability.

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?

With no output schema, the description carries the return-shape burden and does so: it enumerates the returned columns and their meanings, flags nullable values, and explains the pagination contract. Coverage limits and the sibling handoff complete what an agent needs to call it correctly.

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 defaults and formats are already documented; the description nonetheless adds the undocumented 500-symbol cap and frames `symbols` as a bulk-change-detection mechanism rather than a mere filter. It does not restate `limit` semantics, which is fine since the schema handles that.

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 ('Companies that filed quarterly results in a time window, newest first') plus the grain ('one row per company and quarter'). It also names the sibling it is not for offloading to ('call get_financials only for the stocks that changed'), so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Gives the canonical question it answers ('who reported today'), the batch mode with a concrete cap (`symbols` up to 500), and an explicit alternative workflow — use get_financials only for changed stocks rather than for bulk screening. The pagination continuation instruction (`meta.has_more` → `since`/`meta.since`, `until`/`meta.next_until`) tells the agent exactly what to do when results are truncated.

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.