Skip to main content
Glama

Export a size chart

export_agent_ready_chart
Read-onlyIdempotent

Writes a valid SizeRef chart v1 as SizeRef JSON, schema.org JSON-LD, CSV and plain text, and lists anything left out and why. 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. jsonld is a whole block, ready to paste into the product page, with its JSON escaped so no value can end the block. jsonld_note says how the theme can link each variant size to the matching @id; that step is optional.

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": {
      "chart_v1": "<chart_v1>"
    },
    "name": "export_agent_ready_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatsNo
productNo
chart_v1Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured fields. Beyond that, the description adds genuinely new behavior: strict size/column/character limits, the fact that omitted content is listed with reasons, and the detail that the JSON-LD is a complete, escaped <script> block safe from injection plus what jsonld_note conveys. The only gap is that it does not describe the shape of the non-JSON outputs.

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 text is front-loaded with the purpose and the input-scope clarification before the limits and JSON-LD details, and every clause carries information rather than filler. It is dense and long for a single sentence chain, but the density is justified by the number of constraints and output variants being disclosed.

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?

For a three-parameter tool with a nested object schema, zero schema descriptions and no output schema, the definition supplies what an agent needs: input scope, hard limits, output format inventory, and the semantics of the two JSON-LD-related outputs. The omitted product-object detail is minor relative to how complete the rest of the coverage is.

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% and the schema is deeply nested, so the description carries most of the burden. It successfully explains chart_v1's practical bounds (sizes, columns, label lengths, cell truncation) and the meaning of the four format values. The product object (name, url, brand) is never mentioned, leaving one of the three parameters undocumented in both schema and prose.

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 definition opens with a specific verb ('writes') and resource ('a valid SizeRef chart v1') and enumerates the four output formats, so the agent knows exactly what the tool produces. It also scopes the input negatively ('takes a size chart, never a person's measurements'). It never references the sibling tools (audit_size_chart, normalise_size_chart) or says how it differs from them, which keeps it from 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description supplies hard usage constraints (one call per request, up to 60 sizes, 40 columns/measurements, 64-character labels, 200 characters per cell) and clarifies the expected input type, which is useful context. However, it gives no guidance on when to choose this export over a normalise or audit pass, and no prerequisite or failure-mode notes beyond the numeric limits.

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