Skip to main content
Glama

Humanome

Anatomy picture quiz

quiz_anatomy_structures
Read-onlyIdempotent

Quiz a student on human anatomy with pictures: each question shows one structure lit up on a 3D human body (a bone, muscle, nerve, vessel, brain part or organ) with four names to choose from. Give a topic in the student's words (a region, a system or a lab practical, such as 'upper limb muscles', 'cranial nerves', 'bones of the skull' or 'muscles lab practical'), or the names on the student's own lab list. Use it when a student asks to be quizzed or tested on anatomy or to practise for an anatomy lab practical. Not for physiology calculations, diseases or medical advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "quiz_anatomy_structures"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many questions (1 to 10).
topicNoWhat to be quizzed on, in the student's words: a region, a body system, a structure group or a lab practical.
structuresNoA course's own list of structure names to be quizzed on, used instead of a topic.

Output Schema

NameRequiredDescriptionDefault
kindYes
topicYes
creditNo
questionsYes
unmatchedNo
other_topicsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a read-only, idempotent, closed-world, non-destructive operation, so the safety profile is covered. The description then adds behavior the annotations cannot: questions are image-based multiple choice with four options, and scope is limited to anatomy rather than physiology, disease or advice. It stops short of saying whether the quiz is scored or stateful across calls.

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?

Three sentences, front-loaded with the core action and visual format, then usage, then exclusions. The worked topic examples ('upper limb muscles', 'cranial nerves', 'bones of the skull') are useful but make the middle sentence fairly dense.

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 return values need not be described, and the description covers input phrasing and exclusions well. The only unresolved case is what happens if both 'topic' and 'structures' are supplied, which an agent would have to guess.

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%, so the baseline is 3; the description goes further by explaining that 'topic' should be phrased in the student's own words (region, system, or lab practical) and that 'structures' is used 'instead of a topic', clarifying the mutual-exclusivity the schema does not state. That is real added meaning rather than repetition.

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 and resource ('Quiz a student on human anatomy with pictures') and then pins down the exact interaction format: one structure lit on a 3D body, four candidate names. The structure types listed (bone, muscle, nerve, vessel, brain part, organ) and the picture-quiz framing separate it cleanly from lookup and histology siblings.

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 an explicit trigger ('when a student asks to be quizzed or tested on anatomy or to practise for an anatomy lab practical') and explicit exclusions ('not for physiology calculations, diseases or medical advice'). It does not, however, name a sibling such as quiz_histology_slides as the alternative for non-anatomy quiz requests, so routing is clear only for the positive case.

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