Skip to main content
Glama

Shirt measurements

shirt_measurements
Read-only

The real garment measurements of a shirt (chest all the way around and length, in inches) in each size, from the brand's own chart or other checked sources. Not a body-size chart.

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": {
      "brand": "<brand>",
      "item": "<item>"
    },
    "name": "shirt_measurements"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
sizeNoOptional: just this size.
brandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that, the description adds genuinely useful context: units (inches), what is measured (chest all the way around, length), coverage (every size), and provenance (brand's own chart or other checked sources) — the last being notable given openWorldHint=false.

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?

Two short sentences with zero filler. The core definition comes first, the measurement detail and units second, and the disambiguation clause sits at the end where it works as a quick differentiator.

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 return values, and it does: measurements per size in inches with named dimensions. What remains thin is input specification (what 'brand' and 'item' strings should look like) and any note on missing or unavailable charts.

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 only 33%: only 'size' has a description in the schema. The phrase 'in each size' implies that omitting size returns all sizes, which adds a little meaning, but neither 'brand' nor 'item' is clarified — their expected format and matching behavior are undocumented in both places.

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 resource (real garment measurements of a shirt) and scopes the output precisely: chest circumference, length, in inches, per size, sourced from the brand's chart. The closing 'Not a body-size chart' distinguishes it from the sizing sibling (size_me), though it never names that sibling explicitly.

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 a clear negative condition ('Not a body-size chart'), which effectively tells the agent when to prefer a body-measurement tool instead. It stops short of naming the alternative or stating when this tool should be chosen over what_to_buy, so it falls short of full when/when-not/alternatives coverage.

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