Skip to main content
Glama

describe_term

Retrieve the definition, parent classes, synonyms, multilingual names, and relations for a single ontology term to answer entity-specific livestock-health questions.

Instructions

Definition of one ontology term: what it is, its parent classes, synonyms, names in other languages and its relations (which disease a pathogen causes, which species it affects, the neighbours of a country). Pass ONE term, not a sentence. Use it for "What is BRSV?", "Is PI3 a virus?", "Which countries border Belgium?" (term: Belgium).

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

Input Schema

NameRequiredDescriptionDefault
termYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the shape of the response (definition, parents, synonyms, translations, relations), which is the main behavioral fact an agent needs. It omits lookup-failure behavior (what happens for an unknown or ambiguous term) and whether matching is exact or fuzzy, which matters for a 0%-documented string parameter.

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?

The return contents are front-loaded, the single constraint follows, and the examples close. Every sentence adds information; there is no restatement of the tool name or filler.

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 lookup with no output schema and no annotations, the description covers what the tool takes, what it returns, and when to reach for it, which is nearly the whole picture. Only error/ambiguity handling is missing, a minor gap given the tool's simplicity.

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%, so the description must define the single 'term' parameter, and it does: pass a single entity name rather than a sentence, with 'Belgium' as a worked example of the expected granularity. Case sensitivity and disambiguation of homonymous terms are left unstated, keeping it short of a 5.

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 (describe) and resource (one ontology term) and enumerates exactly what the response contains: definition, parent classes, synonyms, multilingual names, and relations. The parenthetical relation examples (pathogen-to-disease, species affected, country neighbours) make the scope concrete, and the 'one term, not a sentence' line implicitly separates it from the search_terms sibling.

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?

Three concrete example questions ('What is BRSV?', 'Is PI3 a virus?', 'Which countries border Belgium?') show precisely when this tool is the right call. It also gives a negative constraint ('Pass ONE term, not a sentence'), which steers the agent away from free-text queries, but it never names the alternative tool to use for multi-word or exploratory queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.