Skip to main content
Glama

Dictionary of Applied Machine Learning

Read one entry

lookup_term
Read-onlyIdempotent

The full dictionary entry for one term: its abstract, its definition, the works it cites and its cross-references. Use it when a specific term is already known; use search_terms when it is not.

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

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

A4.5/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 behavior, so the safety profile is covered. The description adds real value by disclosing the shape of the payload (abstract, definition, cited works, cross-references), which matters because no output schema exists. It stops short of describing size or truncation behavior for very large entries.

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, both load-bearing. The content enumeration comes first and the disambiguation rule second, which is the right ordering for an agent deciding whether to call this or search.

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?

For a single-parameter lookup with no output schema, the description supplies exactly the missing piece — what the entry contains — while the schema handles input formats and failure messaging. Nothing an agent needs to call it correctly is absent.

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 schema itself is unusually rich, covering key-vs-display-name input, case insensitivity, fuzzy tolerance and the not-found fallback. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 resource and scope — 'the full dictionary entry for one term' — and enumerates its contents (abstract, definition, citations, cross-references). It is immediately distinguishable from the sibling search_terms, which is named explicitly.

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 routing rule: use this tool when the term is already known, and use search_terms when it is not. Both the when and the alternative are spelled out, leaving nothing to inference.

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.