Skip to main content
Glama

Audit a size chart

audit_size_chart
Read-onlyIdempotent

Checks a size chart and reports what is wrong with it or still unanswered, without changing it. 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. Send a chart in SizeRef chart format v1, or a table as html, csv, or headers and rows. variant_sizes compares the chart's size labels with the product's; 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. results[] holds one result per table found; the top-level verdict is the worst table's, so read results[] for each table. It cannot see the product page, so a pasted table is at best needs_fix until normalise_size_chart gets the answers.

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

Input Schema

NameRequiredDescriptionDefault
chartNo
tableNo
product_textNo
product_titleNo
variant_sizesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive, and the description adds substantial behaviour beyond them: hard limits (one call per request, 60 sizes, 40 columns/measurements, 64-character labels, 200 characters per cell) and the important constraint that it cannot see the product page, capping pasted tables at needs_fix. It also explains that results[] carries one entry per table and that the top-level verdict reflects the worst table, which prevents misreading a multi-table response.

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?

The purpose and the 'does not change it' constraint are front-loaded, and the remaining sentences cover limits, input formats, parameter roles, and return shape in a tight order. It is dense and unformatted, which makes the limits sentence slightly hard to parse, but no sentence is filler.

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?

With no output schema, the description still describes the response shape (results[] per table, worst-table top-level verdict) and the needs_fix ceiling, which is exactly the return-value context an agent needs. Combined with input formats, size limits, and the normalise_size_chart handoff, nothing material is missing for a nested-schema tool with zero annotation-documented parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 does: it explains that chart accepts SizeRef chart format v1 and that table accepts html, csv, or headers plus rows, covering the nested object's alternatives. It also explains the roles of variant_sizes, product_title, and product_text, so all five parameters gain meaning the bare schema does not provide.

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: it checks a size chart and reports problems or unanswered items, explicitly without modifying it. It also draws the boundary against the sibling by saying a pasted table stays needs_fix until normalise_size_chart supplies the answers, so an agent can tell the audit tool from the fix tool without opening a schema.

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?

The description gives clear conditions: it takes a chart and never a person's measurements, and it is the read-only step that precedes normalise_size_chart. It also assigns each optional parameter a job (variant_sizes compares labels, product_title governs hip handling for long tops, product_text supplies fit when the table doesn't). It stops short of an explicit 'do not use this when…' statement, which keeps it at 4 rather than 5.

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