Skip to main content
Glama

Find Keyword

tt_find_keyword
Read-onlyIdempotent

Resolve a natural-language phrase to the RIGHT Tradetron keyword(s).

Complements tt_lookup_keyword (exact, by name/id) and tt_list_keywords_by_category (browse). USE WHEN the user states logic in natural words ("volume spike", "exit at 30% loss", "value at the last pivot", "previous candle high") and you need the matching keyword + how to use it. Scores the phrase against curated intent->keyword hooks and the live catalog; NEVER invents — a no-match returns honest "browse the category / ask the user" guidance.

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_find_keyword"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/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 safety is covered. The description adds real behavioral detail beyond that: it scores against curated intent hooks plus the live catalog rather than guessing, and on no-match it returns guidance to browse or ask the user instead of fabricating a keyword. It does not discuss scoring thresholds or ranked result count, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core verb phrase, then sibling disambiguation, then the trigger condition, then the guarantee. Slightly redundant in restating the alternative tools twice, but no sentence is filler.

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?

No output schema exists, and the description still tells the agent what comes back: the matching keyword plus how to use it, or honest no-match guidance. For a one-parameter, read-only resolver, nothing essential is missing.

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 0% and the single 'query' param is undocumented in the schema, so the description must carry the meaning. The example phrasings make clear that query is free-form natural language rather than an exact keyword name, which is the key semantic distinction; it could still say more about length or phrasing expectations.

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 specific verb and resource: 'Resolve a natural-language phrase to the RIGHT Tradetron keyword(s)'. It immediately distinguishes itself from tt_lookup_keyword (exact by name/id) and tt_list_keywords_by_category (browse), so an agent can pick it 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?

Gives an explicit trigger condition with literal example phrasings ('volume spike', 'exit at 30% loss', 'previous candle high') and names both alternatives with their distinct roles. When-to-use and when-to-use-something-else are both covered.

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