Skip to main content
Glama

TejHQ Indian Markets

One stock's unusual days

unusual_history
Read-onlyIdempotent

Every day one NSE stock was flagged unusual over a date range, with the same fields as unusual. Use it to see how often a stock does this, and look up what followed with adjusted. Required: symbol. Without from and to it returns the last 90 days. Up to 250 rows per call, oldest first. Coverage: NSE from 2010. Tier: needs a Retail or Pro key (https://tejhq.dev/upgrade).

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": {
      "symbol": "<symbol>"
    },
    "name": "unusual_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast date, inclusive. Default: today. Format YYYY-MM-DD.
fromNoFirst date, inclusive. Default: 90 days before to. Format YYYY-MM-DD.
limitNoMost rows to return.
offsetNoRows to skip, for paging. Use meta.next_offset from a truncated result.
signalNoOnly this signal.
symbolYesExchange ticker, for example RELIANCE, TCS, M&M. Case does not matter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, and the description adds non-obvious operational context on top: a 90-day default window, a 250-row cap with oldest-first ordering, NSE-only coverage from 2010, and an authentication tier requirement. The tier/key note is exactly the kind of prerequisite an agent cannot get from annotations or schema.

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 sentences, each carrying distinct load: purpose, use case plus alternative, required/default parameters, and limits/coverage/tier. Purpose and scope are front-loaded before the constraint details, with no 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?

With no output schema, the description supplies row ordering, the row cap, and deferral to `unusual` for field definitions, plus coverage boundaries and key tier — enough to call and interpret results. The return shape is only defined by reference to a sibling, which is a small but real dependency for an agent that has not read `unusual`.

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 the schema already documents `from`, `to`, `limit`, `offset`, `signal` and `symbol` with formats, defaults and bounds. The description only restates the required `symbol` and the default date window, which the schema already encodes as a default, so it adds little parameter-level meaning beyond that baseline.

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?

"Every day one NSE stock was flagged unusual over a date range" states a specific verb-equivalent (flag), a precise resource (unusual days for a single symbol), and a scope (one stock), which cleanly separates it from the catalog-wide `unusual` sibling. The pointer that results carry "the same fields as unusual" further removes ambiguity about what is returned.

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 an explicit use case ("see how often a stock does this") and routes follow-up analysis to a named alternative, `adjusted`, with the condition for doing so. There is no explicit when-not guidance, but the single-stock scope plus the `adjusted` hand-off make the routing decision clear.

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