Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Market Pulse

get_market_pulse
Read-onlyIdempotent

Today's snapshot: FII/DII net flows (crores), Nifty 50 PE/PB/DY, India VIX, global indices (S&P 500, Dow, Nasdaq...), gold/silver/crude closes, USD/INR. Quick daily overview. For the technical signal scanner (52-week highs/lows, RSI extremes, MACD, volume spikes) use get_market_data with dataset: "signals"; for top gainers/losers/most-active use get_trending_stocks.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds that results are "

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?

About 45 words, front-loaded with the snapshot framing, then a compact field list, then the alternative-routing sentence. Every clause either scopes the contents or prevents a misfire against a sibling; nothing is filler.

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?

For a zero-parameter, read-only snapshot tool with no output schema, the description covers what comes back well enough to select it. Minor gaps remain: no mention of staleness, weekend/holiday behavior, or whether all sections are always present.

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?

There are zero parameters, so there is no schema semantics to add to and the baseline is 4. The description correctly implies a no-argument call by framing the tool as a fixed daily snapshot.

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 concrete verb+resource framing ("Today's snapshot") and then enumerates the exact contents: FII/DII net flows in crores, Nifty 50 PE/PB/DY, India VIX, global indices, commodities, USD/INR. This lets an agent distinguish it from siblings like get_fii_dii_flows or get_india_vix, which cover subsets of the same data.

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?

It explicitly routes the agent away from this tool in two named cases: technical signals (52-week highs/lows, RSI, MACD, volume spikes) go to get_market_data with dataset: "signals", and gainers/losers/most-active go to get_trending_stocks. Both the when-to-use and the when-not-to-use conditions are stated rather than inferred.

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.