Skip to main content
Glama

Tapetide - Indian Stock Market MCP

IPO Detail

get_ipo
Read-onlyIdempotent

One IPO by name or slug: timetable to refund, demat credit and listing; lots and amounts per category; shares reserved incl. anchor and market maker; anchor book with lock-in dates; latest bids per category (times, shares, INR crore, time); latest grey market premium (unofficial) with sauda; KPIs, financials, objects, peers. Application counts are not available.

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_ipo"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCompany name or slug, e.g. "tonbo imaging".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuine value by labeling the grey market premium as "(unofficial)" and by disclosing that application counts are unavailable — a boundary an agent would otherwise waste a call discovering. It says nothing about freshness, pagination, or failure behavior when the name matches nothing.

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 the identity of the resource, then a dense payload inventory with no filler sentences. The bid enumeration "(times, shares, INR crore, time)" is garbled — "time" appears twice — which is the only real blemish on an otherwise efficient definition.

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?

No output schema exists, so the description carries the return-value burden and does so thoroughly, listing most of the substantive fields. For a single-parameter read tool with full annotation coverage, this is nearly sufficient; only lookup-failure and freshness behavior remain unstated.

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?

With one parameter at 100% schema coverage, the schema already documents the query field and even gives an example. The phrase "by name or slug" restates and slightly reinforces that both forms are accepted, but adds no new syntax or matching-rule detail.

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?

"One IPO by name or slug" states a specific resource and lookup key, and the colon-list enumerates exactly what the record contains (timetable, lots, anchor book, bids, GMP, KPIs, peers). It is unambiguous what the tool returns, though it never names a sibling it must be chosen over.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance relative to any alternative tool; the agent must infer from the tool name that this is the IPO-detail endpoint. The closing note "Application counts are not available" is a data limitation, not routing guidance.

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.