Skip to main content
Glama
tresor4k

macalc

calculate_shoe_size

Convert shoe sizes between EU, US, UK, and Japanese systems for international shopping.

Instructions

Convert shoe size between EU, US, UK, and Japanese systems. Use for international shopping. Inputs: size, from-system, to-system, gender. Returns equivalent. See list_bundles for related 'conversions' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeYesShoe size
from_systemYesFrom system

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior2/5

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

No annotations provided. Description only says 'Returns equivalent' without disclosing default behavior for missing parameters or handling of unsupported systems.

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

Conciseness3/5

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

Brief but includes inaccurate details. Could be improved by matching schema exactly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, return values may be covered, but parameter misalignment and missing systems leave the tool incomplete.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers parameters with basic descriptions. The description adds 'to-system' and 'gender' not in schema, causing confusion rather than clarity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool converts shoe sizes between systems, which is clear. However, it mentions Japanese system and parameters (to-system, gender) not present in the schema, causing misalignment.

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?

Suggests use for international shopping and references list_bundles for related calculators, but lacks explicit when-not-to-use or alternative differentiation.

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/tresor4k/macalc-mcp'

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