Skip to main content
Glama

Calculate leather hide quantity

calculate_leather
Read-only

Convert an upholstery job into hides of leather. Leather is sold by the hide in square feet, not by the metre, and hides are an irregular shape with unusable belly and edges, so the conversion is not obvious. Use whenever someone asks how much leather, or how many hides, a chair or sofa needs. Accounts for the finish (aniline leathers cut less economically because every mark shows) and for deep buttoning. Returns square feet, square metres, and hides both as halves and as whole hides.

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

Input Schema

NameRequiredDescriptionDefault
pieceNoFurniture type. Options: drop-in dining seat, dining chair seat and back, occasional chair, club armchair, wing-back armchair, recliner armchair, 2-seat sofa, 3-seat sofa, 4-seat sofa, footstool, ottoman, headboard double, boxed seat cushion
finishNoDefault pigmented / corrected grain.
fabric_metresNoAlternative to "piece": the metres of 137 cm fabric the job would take.
deep_buttoningNoAdds 30%.
hide_size_sqftNoAverage hide size. Default 50 sq ft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive, so the safety profile is covered; the description goes further by explaining what the calculation accounts for (finish economy, deep buttoning) and what it returns (sq ft, sq m, hides in halves and whole hides) — valuable since there is no output schema. It does not say what happens when neither 'piece' nor 'fabric_metres' is supplied, which is a real behavioral gap given zero required parameters.

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?

Four tight sentences, front-loaded with the conversion statement, then the reason the conversion is non-obvious, then the use case, then outputs. The explanation of irregular hide shape earns its place by justifying the tool's existence, though the return-value sentence slightly overlaps what the output could state if a schema existed.

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 return values and does so adequately (three unit forms, halves and whole hides), and it explains the modelling complexities (finish, deep buttoning). It stops short of covering the piece-vs-fabric_metres mutual exclusivity rule and default assumptions beyond hide size, which an agent would still have to infer.

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 coverage is 100%, so baseline is 3, but the description adds genuine meaning beyond the schema by explaining why finish matters — aniline leathers cut less economically because every mark shows — which is the rationale the enum values alone do not convey. It adds less for hide_size_sqft and fabric_metres, whose semantics live entirely in the schema.

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: 'Convert an upholstery job into hides of leather', and immediately frames the domain (leather sold by hide in square feet, irregular shapes) that separates it from the fabric-based sibling calculation. An agent can tell this is the hide-quantity tool, not a general area or fabric tool.

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 a clear trigger: 'Use whenever someone asks how much leather, or how many hides, a chair or sofa needs.' It does not name a specific alternative tool or state when-not to use it (e.g. when the user supplies fabric metres or wants an estimate rather than a hide count), but the usage context is unambiguous.

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