Skip to main content
Glama

tm_query

Query translation memory (hybrid retrieval; free).

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_text": "<query_text>",
      "source_lang": "<source_lang>",
      "target_lang": "<target_lang>"
    },
    "name": "tm_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_kNo
query_textYes
document_idNo
source_langYes
target_langYes
cross_languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions hybrid retrieval and cost, but omits key behavior such as required permissions, result format, pagination, ranking semantics, or how cross_language and document_id affect results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The single sentence is front-loaded and free of wasted wording. However, it is under-sized for a six-parameter retrieval tool with no schema documentation, so brevity comes at the cost of necessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given six parameters, no annotations, no output schema, and zero schema description coverage, the description is not complete enough for reliable invocation. It conveys the basic purpose but leaves the agent without guidance on parameters, return values, or operational constraints.

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

Parameters1/5

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

The schema has 0% description coverage across six parameters, including three required ones. The description adds no meaning for query_text, source_lang, target_lang, top_k, document_id, or cross_language, leaving the agent to infer all parameter semantics from names alone.

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: 'Query translation memory'. The parenthetical 'hybrid retrieval; free' adds a useful qualifier about retrieval mode and cost, but it does not distinguish this tool from sibling tools such as tm_import or other run-related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives. The word 'free' implies cost considerations but does not establish selection criteria or exclusions relative to sibling tools.

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