Skip to main content
Glama

Fetch a MarketPing record

fetch
Read-onlyIdempotent

Retrieve the full content of one record by its id — a company profile with fundamentals and recent announcements; one announcement (id alert:, the id from recent_alerts) with THE FILING'S OWN TEXT, the company's filed XBRL figures when it is a results statement, its measured price reaction and the link to the original document on BSE/NSE (long filings come in parts: alert::2, …); one page of a filing; or one IPO issue. Use this to read a filing — do not try to open the source link. A MarketPing alert link (marketping.in/alerts/… or api.marketping.in/alerts//attachment) is accepted as the id. When the text carries a WARNING about misread figures, quote figures only from the filed figures. Factual data only — MarketPing publishes no buy/sell recommendations, no price targets and no IPO grey-market premium.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn id returned by search, alert:<id> from recent_alerts, or a MarketPing alert link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id returned by search"New value: +"An id returned by search, alert:<id> from recent_alerts, or a MarketPing alert link"
  2. First observed

TDQS

A4.4/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 genuinely new behavior: long filings arrive in parts (alert:<id>:2, …), an announcement includes the filed XBRL figures, price reaction, and source link, and it warns not to open the link. It also states the content policy (factual data only, no recommendations, targets, or grey-market premium) and the WARNING rule about quoting only filed figures. It does not cover size limits, latency, or error behavior for a bad id, so not 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?

The core action is front-loaded in the first clause, and every subsequent clause carries information (record types, parts, link handling, figure-quoting rule). It is dense but somewhat run-on with nested parentheticals, 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 burden of describing what comes back, and it does so for every record variant, including the parts mechanism and the embedded filed figures and price reaction. An agent has enough to call it correctly and to interpret the response, including how to handle warning text in the content.

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 the baseline is 3, but the description goes well beyond the schema by explaining that the id may be a search result, an alert:<id> from recent_alerts, a page part (alert:<id>:2), or a pasted MarketPing alert URL. That resolves the main ambiguity an agent would hit when constructing the parameter.

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 opens with a specific verb and resource ("Retrieve the full content of one record by its id") and then enumerates the exact record types returned: company profile, announcement with the filing's own text, one page of a filing, or one IPO issue. This lets an agent distinguish it from siblings like doc_contents, read_pages, and search_filings without opening any 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?

It gives a clear directive for the primary use case ("Use this to read a filing — do not try to open the source link"), which is an explicit when-to-use plus a when-not. It also tells the agent that an alert link is a valid substitute for an id. It stops short of naming sibling tools or stating when to prefer doc_contents or read_pages instead.

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.