Skip to main content
Glama

Studies per body part, by region

studies_by_region
Read-onlyIdempotent

Use when asked "how much research is there on the thorax" or "which body parts have no studies yet". The Studies per body part key of the Greencyclepedia body map. Give a region (head-neck, thorax, abdomen, pelvis, upper-limb-left, upper-limb-right, lower-limb-left, lower-limb-right) or leave it out for the whole body: the parts by study band (No studies yet, 1 to 99, 100 to 999, 1,000+) with counts, the most studied parts, the parts with no studies yet, the snapshot date, the source and licence and the body map link. A count is the PubMed studies that name the part, from a weekly saved snapshot. Educational reference, not medical advice. Example arguments: {"region":"thorax"}.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many items to return, at most 100.
regionNoA region id or name, for example "thorax", "head-neck" or "left leg", or "whole body". Leave out for the whole body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive, so the bar is lower, and the description still adds real context: counts are PubMed studies naming the part, sourced from a weekly saved snapshot with an exposed snapshot date and licence. It also flags the educational-reference/not-medical-advice stance and supplies a worked example call. Minor gap: it does not say how stale the weekly snapshot can be or how truncation/LIMIT affects the returned tallies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead-in use-case phrases and the trailing example call are well placed, but the middle is a single sprawling sentence that chains six return artifacts plus provenance, licence and link into one run-on list. It is informative yet noticeably harder to scan than it needs to be.

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 no output schema, the description carries the burden of describing returns and does so thoroughly: band definitions, counts, highlights, snapshot date, source/licence and link. An agent can call it correctly. What is missing is only edge behavior, such as what happens with an unrecognized region string or how limit interacts with banded aggregates.

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, but the description earns an extra point by enumerating all eight valid region ids (head-neck, thorax, abdomen, pelvis, upper/lower limbs) which the schema only samples via three examples. The limit parameter is left entirely to the schema, which is acceptable given the schema documents it fully.

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 states a specific resource (studies per body part) and its aggregation key (region on the Greencyclepedia body map), and it enumerates what comes back: banded counts, most-studied parts, unstudied parts, snapshot date, source/licence, map link. It never names a sibling it differs from, so the agent must infer why this differs from find_studies or ask_atlas, which keeps it below a 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?

It gives two concrete triggering questions ("how much research is there on the thorax", "which body parts have no studies yet") that map cleanly onto the tool's output. It also states the optional-region behavior explicitly ("leave it out for the whole body"). No when-not condition or named alternative is offered, so it stops at 4.

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.