Skip to main content
Glama

TejHQ Indian Markets

Liquidity universe

universe
Read-onlyIdempotent

Point-in-time members of liquid100, liquid250 or liquid500: the top instruments by trailing 63-trading-day turnover at the latest monthly rebalance on or before as_of. Delisted names stay in the months they qualified for. Required: name. Returns 100 rows by default, up to 500, by rank. Coverage: NSE from 2010-01-04, BSE from 2024-07-08. 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": {
      "name": "<name>"
    },
    "name": "universe"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesUniverse name.
as_ofNoDate to read the universe on. Default: today. Format YYYY-MM-DD.
limitNoMost rows to return.
offsetNoRows to skip, for paging. Use meta.next_offset from a truncated result.
exchangeNoExchange. Default nse.

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 declare readOnly/idempotent/non-destructive/closed-world, so safety is covered; the description adds substantial behavior beyond that: point-in-time snapshot semantics tied to a monthly rebalance, survivorship handling ('Delisted names stay in the months they qualified for'), data coverage start dates, auth tier requirement, and the result-size/ordering contract (100 default, up to 500, by rank).

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?

Dense but front-loaded: the definition and ranking rule come first, followed by behavior, then coverage and auth constraints. Almost every clause carries information; the only wasted fragment is 'Required: name', which merely restates the schema's required array.

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?

Strong for a 5-parameter read tool with no output schema: row count default and maximum, ordering by rank, and coverage boundaries are all stated. The one remaining gap is the exact fields present in each returned row, a minor omission but a real one given no output schema exists to document them.

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. The description goes further by explaining the meaning behind name and as_of — what the universes represent, that turnover is a trailing 63-trading-day measure, that as_of snaps to the latest rebalance on or before the date, and that delisted names remain — which the schema does not convey.

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 precise resource (point-in-time membership of liquid100/liquid250/liquid500) and the exact ranking rule (top instruments by trailing 63-trading-day turnover at the latest monthly rebalance on or before as_of). No sibling name overlaps this resource — screener/symbols are different objects — so an agent can distinguish it 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides contextual constraints that implicitly guide use: coverage windows (NSE from 2010-01-04, BSE from 2024-07-08), the tier/key requirement, and the point-in-time semantics of as_of. However, it never says when to prefer this over a universe-like alternative (e.g. screener or symbols) or when not to call it, so the routing guidance is only implied.

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