Skip to main content
Glama

Dictionary of Applied Machine Learning

Search the dictionary

search_terms
Read-onlyIdempotent

Search the term names, abstracts and definitions for a keyword or phrase and return the best matches, each with its abstract. Use it when the right term is not known in advance.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many matches to return, best first. Defaults to 8.
queryYesThe words to search for, e.g. 'overfitting' or 'gradient step size'. Matching is case-insensitive; a term whose name contains the query ranks above one where only the definition does.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit / default
      Added value: +8
    • addedInput schema / properties / limit / description
      Added value: +"How many matches to return, best first. Defaults to 8."
    • addedInput schema / properties / limit / maximum
      Added value: +50
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / query / description
      Added value: +"The words to search for, e.g. 'overfitting' or 'gradient step size'. Matching is case-insensitive; a term whose name contains the query ranks above one where only the definition does."
    • addedInput schema / properties / query / minLength
      Added value: +1
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds the useful disclosure that results are ranked 'best matches' and that each carries its abstract, which is the only return-shape information available since there is no output schema.

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, zero filler: the search scope and return content come first, the usage condition second. Nothing is repeated from the schema or annotations.

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 simple read-only search with complete annotations and a fully documented two-parameter schema, the description covers scope, ranking and return shape. It does not mention the result limit or what happens with zero matches, minor gaps given the schema already handles limits.

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% and the schema itself documents case-insensitivity, ranking precedence, default limit of 8 and the max of 50. The description adds only the fact that abstracts are searched in addition to names and definitions, which is marginal beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('search the term names, abstracts and definitions') plus the return payload ('best matches, each with its abstract'). It implicitly separates itself from lookup_term by targeting unknown terms, but never names a sibling outright.

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 it when the right term is not known in advance" gives a concrete trigger condition that distinguishes it from exact-lookup siblings like lookup_term. It stops short of naming that alternative or stating when not to use this tool.

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.