Skip to main content
Glama

Normalise a size chart

normalise_size_chart
Read-onlyIdempotent

Turns a size table, or a chart with gaps, into SizeRef chart format v1 from what the table states plus the answers you pass. Nothing is inferred from the numbers. Takes a size chart, never a person's measurements. Limits: one call per request; up to 60 sizes, 40 columns or measurements a size, and 64 characters a size label or measurement name; each table cell is read up to 200 characters. When something is left open it returns questions with the allowed answers instead of a chart. A page with several tables needs table_index. product_title decides whether hips are kept for long tops such as a kurta or a dress; product_text gives the fit when the table does not state it.

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

Input Schema

NameRequiredDescriptionDefault
chartNo
tableNo
answersNo
table_indexNo
product_textNo
product_titleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), and the description layers on substantial context beyond that: hard limits (60 sizes, 40 columns, 64-char labels, 200-char cells), one call per request, and the key behavioral trait that incomplete input returns questions with allowed answers instead of a chart. It also discloses that nothing is inferred from the numbers.

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?

Purpose is front-loaded in the first clause, then constraints, then parameter effects; every sentence carries information. The run of numeric limits is dense but justified, and there is no filler.

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?

For a six-parameter tool with nested objects and no output schema, the description covers input constraints, failure mode (questions back instead of a chart), and the parameters that change behavior. Residual gaps are the detailed structure of the chart/table payloads, which the agent must read from the schema.

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 description coverage is 0%, so the description must carry the load, and it explains the nontrivial parameters well: table_index for multi-table pages, product_title's effect on hip retention, product_text as a fit fallback, and answers as the mechanism for resolving open questions. It says less about the shape of chart versus table inputs (csv/html/rows/headers/caption), leaving part of the nested schema unexplained.

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?

States a specific verb and resource ('Turns a size table, or a chart with gaps, into SizeRef chart format v1') and adds sharp scope boundaries ('Takes a size chart, never a person's measurements'). An agent immediately knows what goes in and what comes out.

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?

Gives clear conditions for use: a page with several tables needs table_index, product_title decides whether hips are kept for long tops, and product_text supplies fit when the table omits it. It stops short of naming the sibling alternatives (audit_size_chart, export_agent_ready_chart) or when to prefer them, so no explicit routing.

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