Skip to main content
Glama

Humanome

List what a lab practical asks

list_lab_practical_structures
Read-onlyIdempotent

List the structures an anatomy and physiology lab practical asks, section by section (for example the bones, the muscles, the brain, the heart, blood vessels, the nervous system, A&P 1 or A&P 2), with links to practise each. Use it when a student asks what to study for a lab practical or wants a checklist of structures.

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

Input Schema

NameRequiredDescriptionDefault
practicalYesThe practical or course unit, e.g. 'muscles', 'appendicular skeleton', 'A&P 2'.

Output Schema

NameRequiredDescriptionDefault
idYes
titleYes
totalYes
page_urlNo
sectionsYes
virtual_labNo
practice_3d_urlNo
other_practicalsNo

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 readOnlyHint, idempotentHint, and openWorldHint=false, so safety and side-effect behavior are covered. The description adds that results are organized section by section and include practice links, which is modestly useful. It does not say how an unrecognized or ambiguous 'practical' value is handled.

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 core action, then the usage trigger. The parenthetical list of sections is long but earns its place by showing the free-text range the parameter accepts.

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?

An output schema exists, so return values need no explanation, and annotations cover safety and openness. For a single free-text parameter list tool, the description supplies everything needed to call it correctly, with only minor ambiguity around fuzzy matching.

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 coverage is 100% and the single parameter is fully documented, so the schema carries the load; baseline 3 applies. The description's examples ('the bones, the muscles, the brain, the heart, blood vessels, A&P 1 or A&P 2') largely restate what the schema's example already conveys, adding breadth of accepted terms but no new syntax or matching rules.

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?

Specific verb plus resource: 'List the structures an anatomy and physiology lab practical asks, section by section' with links to practise each. This clearly separates it from the quiz_* and look_up_* siblings by output shape (checklist with links, not questions or a single record). It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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 asks what to study for a lab practical or wants a checklist of structures' gives a clear triggering condition. There is no when-not guidance (e.g., use look_up_anatomy_structure for one specific structure's details), so alternatives are left implicit.

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