Skip to main content
Glama

Humanome

Histology slide quiz

quiz_histology_slides
Read-onlyIdempotent

Quiz a student on identifying tissues on real microscope slides (epithelial, connective, muscle and nervous tissue): each question shows a slide with its magnification and four tissue names, the wrong ones being tissues that look alike. Use it when a student wants to practise tissue identification or a histology practical.

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_histology_slides"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many slides (1 to 10).
tissue_typeNoWhich kind of tissue, or all.all

Output Schema

NameRequiredDescriptionDefault
kindYes
topicYes
creditNo
questionsYes
unmatchedNo
other_topicsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: each question presents a slide with its magnification plus four tissue names, with distractors deliberately chosen as look-alike tissues. It does not describe scoring, feedback on wrong answers, or quiz progression, but an output schema exists to carry return values.

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 that front-load the purpose before the usage cue, with no filler or repeated title text. The parenthetical tissue list and the look-alike-distractor clause are both informative, though the single long first sentence packs several ideas together.

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?

With only two fully documented optional parameters, a rich annotation set, and an output schema, the description covers what an agent needs to invoke it. The one remaining gap is how a session behaves after questions are served, which the output schema plausibly covers.

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%, with both optional parameters documented including the enum values and the 1-10 range, so the schema carries the full explanatory burden. The description only implies that 'count' maps to the number of slides ('each question shows a slide') and never mentions tissue_type, adding no meaning beyond the schema.

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 and resource ('Quiz a student on identifying tissues on real microscope slides') and enumerates the covered tissue categories, so an agent can tell this is an interactive histology quiz rather than a lookup. It stops short of explicitly contrasting itself with the sibling quiz_anatomy_structures, leaving the agent to infer the subject-matter split from the tissue list alone.

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 when a student wants to practise tissue identification or a histology practical' gives a clear triggering context tied to a learner's intent. There are no stated exclusions or named alternatives, so an agent must decide on its own that list_lab_practical_structures and look_up_anatomy_structure are not substitutes when the goal is practice rather than reference.

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