Skip to main content
Glama

Look Up Keyword

tt_lookup_keyword
Read-onlyIdempotent

Look up one Tradetron keyword by display name, function name, or ID.

Returns full catalog entry: param signature, types, defaults, example, description, and category.

Use this whenever you're about to use a keyword and want to confirm its parameters. Cheaper than guessing — the validator will reject unknown keywords or wrong param counts.

Examples of valid queries: 'ATR', 'tt_PNL', 'Net Delta', 'Positions Detail', '18'.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered by structured data. The description's added value is the disclosure that a full catalog entry is returned and that downstream validation rejects unknown keywords or wrong param counts. It does not say what happens when the query matches nothing (error vs. empty), which is the one behavioral detail an agent actually needs here.

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?

Front-loaded with purpose then return shape, then usage, then examples — a sensible ordering with no filler sentences. The example list is the longest block but is the highest-value content for disambiguating accepted query formats, so it earns its place. Slightly more compact prose around the examples would make it tight.

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 one-parameter, non-destructive lookup with no output schema, the description covers purpose, return contents, invocation context, and accepted input forms. The remaining gaps are the no-match behavior and its relationship to tt_find_keyword, neither of which blocks a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the lone parameter is titled only "Query", so the description carries the whole burden — and it does: it names the three accepted identifier forms (display name, function name, ID) and gives five worked examples spanning symbolic ('ATR'), prefixed ('tt_PNL'), human-readable ('Net Delta', 'Positions Detail') and numeric-as-string ('18'). That is enough for an agent to construct a valid query on the first attempt without trial and error.

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?

"Look up one Tradetron keyword by display name, function name, or ID" gives a specific verb, resource, cardinality (one), and the three identifier forms. It also enumerates what comes back (param signature, types, defaults, example, description, category), so the agent knows exactly what it gets. It stops short of distinguishing itself from the sibling tt_find_keyword, leaving the single-vs-search contrast implicit.

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?

"Use this whenever you're about to use a keyword and want to confirm its parameters" supplies a concrete triggering context and even a cost rationale ("Cheaper than guessing") plus the consequence of skipping it (validator rejects unknown keywords or wrong param counts). No when-not-to-use case or explicit alternative is named, which is the only thing separating this from a 5.

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