Skip to main content
Glama

TejHQ Indian Markets

Find a symbol from a name

resolve
Read-onlyIdempotent

Maps free text, such as a company name or a former ticker, to exchange symbols with a match score. Required: query, 2 to 80 characters. Returns 5 matches by default, up to 25. 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": {
      "query": "<query>"
    },
    "name": "resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost rows to return.
queryYesCompany name or ticker, for example Reliance Industries.
exchangeNoExchange to search. Default both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description rightly spends its words elsewhere: it discloses the auth/tier gate (Retail or Pro key with an upgrade URL), the default of 5 matches and ceiling of 25, and that results carry a match score. It still omits what happens when no match is found, which keeps it from a 5.

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?

Two sentences, front-loaded with the core mapping behavior, then required-input and result-count facts, then the access tier. No filler and no repetition of the title.

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 three-parameter lookup with no output schema, the description covers purpose, input minimum, default and maximum result size, scoring of matches, and access prerequisites. Only the no-match/error behavior and the exchange scoping are left unaddressed.

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 coverage is 100%, so the schema already documents all three parameters; the description adds little beyond restating the query concept and the default/cap on results. Worse, its 'query, 2 to 80 characters' constraint conflicts with the schema's minLength 1 and absent maxLength, and the exchange parameter is never mentioned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Maps free text ... to exchange symbols') plus the distinguishing output trait ('with a match score'), which separates it from a plain symbol listing. It does not name or contrast any sibling tool, so it stops short of a 5.

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?

Usage context is implied by 'free text, such as a company name or a former ticker' and hardened by prerequisites ('Required: query', tier/key requirement), but there is no explicit when-to-use vs when-not guidance and no pointer to an alternative such as 'symbols' for exact-symbol lookups.

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