Skip to main content
Glama

Dictionary of Applied Machine Learning

Follow the cross-references

get_related_terms
Read-onlyIdempotent

The terms one entry cross-references, its See-also list, each with its abstract. Use it to widen a topic by one step from a term already in hand.

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": {
      "term": "<term>"
    },
    "name": "get_related_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesA term, given either as its key (the lowercase one-word identifier, e.g. 'erm', 'gradientdescent') or as its display name (e.g. 'empirical risk minimization'). Matching is case-insensitive and tolerates small differences in spelling; an input that resembles no published term returns a message saying so rather than a wrong entry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / term / description
      Added value: +"A term, given either as its key (the lowercase one-word identifier, e.g. 'erm', 'gradientdescent') or as its display name (e.g. 'empirical risk minimization'). Matching is case-insensitive and tolerates small differences in spelling; an input that resembles no published term returns a message saying so rather than a wrong entry."
  2. First observed

TDQS

A3.6/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 and repeatability need no restating. The description adds the useful return-shape detail that each related term comes with its abstract. With no output schema, a fuller statement of the return structure (keys vs display names, behavior when an entry has no cross-references, result count) would be expected.

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?

Two short sentences with no filler; the return content is front-loaded before the usage hint. The first sentence is a verbless noun phrase, which reads slightly clipped, but nothing is redundant.

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, read-only, non-destructive lookup, the description plus annotations cover what the agent needs to decide to call it. Remaining gaps are modest: whether returned terms are keys or display names, and what happens when an entry has no cross-references (the sibling schema documents an analogous no-match message, but this description does not).

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 description coverage is 100% and the single parameter is documented in detail, including key-vs-display-name input, case insensitivity, fuzzy matching, and the no-match message. The description only echoes the idea of a term 'already in hand,' adding essentially nothing beyond the schema, so the 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?

The description names a specific verb-equivalent action and resource: it returns the terms that one entry cross-references (its See-also list), each with its abstract. That is clearly distinct from lookup_term (fetching an entry itself) or search_terms. It stops short of naming those siblings explicitly, so differentiation is inferable rather than stated.

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 to widen a topic by one step from a term already in hand' gives a concrete triggering condition: the caller must already hold a term and want to expand rather than search or look up. There is no explicit when-not guidance or named alternative (e.g. 'use search_terms if you have no term yet'), which keeps it below 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.