Skip to main content
Glama

Calculate a deep-buttoning layout

calculate_deep_buttoning
Read-only

Work out a deep-buttoned diamond layout: how many buttons, the marking grid on the base, the wider grid on the fabric, and the cut size of the cover. The fabric grid is always larger than the base grid because fabric has to travel down into each button pull — get that wrong and the panel is ruined. Use for buttoned headboards, Chesterfields, ottomans and buttoned chair backs.

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": {
      "area_width_cm": "<area_width_cm>",
      "area_height_cm": "<area_height_cm>",
      "diamond_width_cm": "<diamond_width_cm>",
      "diamond_height_cm": "<diamond_height_cm>"
    },
    "name": "calculate_deep_buttoning"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoButton depth, which sets the fabric fullness. shallow 13 mm, medium 19 mm, deep 32 mm per diamond each way. Default medium.
turn_cmNoTurnings to wrap the frame. Default 5 cm.
border_cmNoPlain unbuttoned border around the diamonds. Default 0.
area_width_cmYesWidth of the area to be buttoned, excluding any plain border.
area_height_cmYesHeight of the area to be buttoned.
diamond_width_cmYesRoughly how wide you want each diamond. Gets adjusted to fit the area evenly.
diamond_height_cmYesRoughly how tall you want each diamond.
fullness_width_mmNoOnly with depth "custom".
fullness_height_mmNoOnly with depth "custom".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds one genuinely useful domain constraint — the fabric grid must be larger than the base grid because fabric travels into each button pull, with a strong warning that getting it wrong ruins the panel. It does not disclose precision, units handling, or rounding of the resulting grids, so it is helpful but not rich.

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 most important information — what is computed — is front-loaded in the first sentence, and the job-type sentence is a compact routing cue. The middle sentence about fabric versus base grid is longer than strictly necessary for concision but earns its place as a correctness warning, so only minor trimming is possible.

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 nine parameters, four required, and no output schema, the description carries the burden of explaining what comes back, and it does so by naming the four outputs explicitly. What is missing is any indication of units, format or precision of the returned grids, which matters for a calculation tool this parameter-rich.

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

Parameters3/5

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

Schema description coverage is 100%, so every one of the nine parameters (including the depth enum with its millimetre values and the custom fullness fields) is already documented in the schema. The description adds no parameter-level meaning beyond that and only alludes indirectly to fullness via the fabric-grid remark, making the baseline 3 correct.

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?

The description opens with a specific verb ("Work out") and a precise resource ("a deep-buttoned diamond layout") and then enumerates the exact deliverables: button count, base marking grid, wider fabric grid, and cover cut size. That level of specificity separates it cleanly from the other calculators in the sibling list, which handle fabric, leather, foam or costs.

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?

"Use for buttoned headboards, Chesterfields, ottomans and buttoned chair backs" gives concrete when-to-use context tied to real upholstery jobs. There are no explicit exclusions or named alternatives, so an agent must infer that unbuttoned or non-diamond work belongs elsewhere, but the positive guidance is clear.

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