Skip to main content
Glama

Tapetide - Indian Stock Market MCP

by com.tapetide
OverviewDiscussionsAdmin

User Watchlist

get_watchlist
Read-onlyIdempotent

Get the user's stock watchlist — the stocks they are following, newest first. Returns symbol, company name, sector, industry and the live quote (price, change, change %, previous close; null when unpriced) for each stock, plus a gainers/losers/unchanged tally of the whole list in movers. Paged: up to 50 stocks per call; when has_more is true, call again with offset: next_offset to get the rest (do this before acting on "all" of a long watchlist).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoStocks per page (default and max 50; larger values are clamped).
offsetNoStart position for paging (default 0). Pass `next_offset` from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Stocks per page (default and max 50; larger values are clamped).",
+  "type": "number"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Start position for paging (default 0). Pass `next_offset` from the previous page.",
+  "type": "number"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description goes well beyond them: it enumerates returned fields, flags that quote fields are null when unpriced, describes the `movers` tally, and explains the 50-per-page clamp plus the has_more/next_offset paging contract. With no output schema, this disclosure is exactly what an agent needs.

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?

A single dense paragraph ordered purpose → returned data → paging mechanics, with no filler. Every clause carries information an agent needs to call the tool correctly.

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?

No output schema exists, so the description must describe returns, and it does so completely: field list, null semantics for unpriced quotes, the movers summary, and the full paging protocol. Nothing needed to invoke or interpret the call is missing.

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?

Schema description coverage is 100%, so both `limit` and `offset` are already documented, including the default/max 50 clamp and the 'pass next_offset' convention. The description restates the same semantics (50 per call, offset: next_offset) without adding format or edge-case detail, so the baseline of 3 applies.

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 ('Get the user's stock watchlist — the stocks they are following') with ordering ('newest first'), which cleanly separates it from add_to_watchlist, remove_from_watchlist and get_user_portfolio. An agent can identify the tool without opening the 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?

Gives explicit operational guidance for the paging loop ('when has_more is true, call again with offset: next_offset') and warns to finish paging 'before acting on all of a long watchlist'. It does not, however, contrast the tool with siblings like get_user_portfolio or search_stocks, so no exclusion guidance is offered.

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

All Tapetide - Indian Stock Market MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources