Skip to main content
Glama

list_body_regions

List valid body region IDs to highlight pain or tightness on a body diagram. IDs and labels are grouped by body area.

Instructions

    List all valid body region IDs that can be highlighted on the body
    diagram or that the athlete might paint as a source of pain or
    tightness. Use this to discover region IDs before calling
    highlight_body_regions.

    Each region has a stable ID (e.g. left_itb_lower) and a human-
    readable label (e.g. "IT band — lower (L)"). Regions are grouped
    by body area.

    Returns:
        Grouped list of region IDs and labels.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses stable IDs, human-readable labels, and grouping by body area. No annotations provided, but description covers behavioral traits adequately for a read-only list tool.

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

Conciseness5/5

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

Three short paragraphs, front-loaded purpose, no wasted words. Well-structured and efficient.

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?

Describes return format (grouped list with IDs and labels). Output schema exists. Lacks mention of static/dynamic nature or prerequisites, but overall sufficient for its purpose.

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?

No parameters; schema coverage is 100%. Description adds no parameter info, but baseline is 4 for zero-parameter tools.

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?

Clearly states it lists valid body region IDs for highlighting or painting, distinguishing it from siblings like highlight_body_regions and get_painted_regions.

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?

Explicitly advises using this tool to discover region IDs before calling highlight_body_regions, providing clear usage context. Could add exclusions for other use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wernerpe/mcpacer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server