Skip to main content
Glama

Humanome

Look up an anatomy structure

look_up_anatomy_structure
Read-onlyIdempotent

Look up one structure of the human body by name (spellings and abbreviations from a lab sheet work too): what it is in one or two sentences, its body system, a picture of it lit on a 3D body, its reference page and the quizzes that ask it. Use it when a student asks what or where a structure is.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe structure's name, e.g. 'deltoid', 'foramen magnum', 'm. sartorius'.

Output Schema

NameRequiredDescriptionDefault
matchesYes
suggestionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/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 useful behavior beyond that, namely tolerance for misspellings and abbreviations and the shape of the result. It says nothing about what happens when the name is ambiguous or unmatched, which matters for a fuzzy-input lookup.

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 sentences, front-loaded with the action and the returned payload, then the usage trigger. The enumerated result list is slightly long but each item is informative, and there is no 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?

An output schema exists, so the description need not explain return values, and the annotations cover side-effect semantics. For a one-parameter lookup it is nearly complete; only the ambiguity/no-match handling is unaddressed.

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 100% and the single parameter already has examples, so the baseline is 3. The description adds genuine meaning beyond the schema by telling the agent that non-canonical spellings and abbreviations from a lab sheet are acceptable inputs.

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?

Strong specific verb+resource: 'Look up one structure of the human body by name', and it enumerates what comes back (definition, body system, 3D image, reference page, quizzes). The word 'one' implicitly separates it from the list-style sibling, but no sibling 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 Guidelines4/5

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

Gives a concrete trigger: 'Use it when a student asks what or where a structure is', and notes that lab-sheet spellings/abbreviations are accepted, which is real routing guidance. It stops short of stating when not to use it or pointing to the quiz/list siblings.

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