Skip to main content
Glama

TejHQ Indian Markets

Pipeline freshness

status
Read-onlyIdempotent

Latest trading date published and when the nightly pipeline last ran. Call this to learn the newest date with data before asking for a snapshot or a recent range. End of day data only, no intraday or live prices. No API key needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the description earns credit for the extra context it supplies: nightly batch cadence, EOD-only coverage with no intraday or live prices, and the fact that no API key is required. It stops short of saying what the response looks like when the pipeline has not run recently or has failed, which is the one behavioral detail an agent probing freshness would want.

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?

Four short sentences, front-loaded with what is returned, then when to call it, then the data limitation, then the auth note. No sentence is redundant and nothing is buried mid-paragraph.

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?

For a zero-parameter, closed-world status tool with annotations covering the safety profile, the description covers return content, invocation timing, data currency limits and auth requirements. There is no output schema, but the description already characterizes the returned values well enough to compensate.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. It implicitly confirms the no-input nature by describing a call that simply returns current freshness state.

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 names the exact payload: the latest published trading date plus the timestamp of the last nightly pipeline run. It also separates this tool from data-fetching siblings by framing it as the freshness probe to call 'before asking for a snapshot or a recent range', so an agent can place it relative to snapshot and range/ohlcv tools without opening a 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?

It gives an explicit trigger ('Call this to learn the newest date with data before asking for a snapshot or a recent range') and an explicit scope boundary ('End of day data only, no intraday or live prices'), which effectively tells the agent when this tool is the wrong choice. Both the when and the when-not are present in two short sentences.

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.

Resources