Skip to main content
Glama

Confirm a part’s exact dimensions

confirm_hardware_dimensions

Records your shop’s confirmation of the exact part and dimensions you stock, so designers can build parts around it. Only confirm a part you have checked: designs are cut to these numbers. Give evidence: a datasheet link or how you measured it. Needs a connected Printlooper account.

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": {
      "offering_id": "<offering_id>",
      "part_number": "<part_number>",
      "shape": "<shape>",
      "width_mm": "<width_mm>",
      "depth_mm": "<depth_mm>",
      "height_mm": "<height_mm>",
      "tolerance_mm": "<tolerance_mm>",
      "evidence": "<evidence>"
    },
    "name": "confirm_hardware_dimensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
shapeYes
depth_mmYesSame as width for a round or hexagonal part
evidenceYesThe datasheet lines, or how and with what it was measured
width_mmYesDiameter for a round part, across flats for a hexagonal part
height_mmYes
source_urlNo
offering_idYesoffering_id from list_my_hardware
part_numberYes
tolerance_mmYes

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?

With annotations only covering the safety flags (not read-only, not destructive, not idempotent), the description adds real context: the numbers become cutting dimensions, so a wrong confirmation has downstream consequences, and a connected Printlooper account is required. It does not say whether confirming again overwrites an earlier confirmation or whether confirmation is reviewed.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and stakes, then the precondition, then the auth requirement. No filler.

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

Completeness3/5

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

For a 9-parameter write tool with no output schema, the description covers the stakes of a mistake but leaves out what the tool returns, whether a prior confirmation is replaced, and the meaning of tolerance and shape values. Adequate but with clear gaps.

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 coverage is 44% and 8 of 9 parameters are required, so the description should compensate more than it does. It clarifies the evidence field ('datasheet link or how you measured it'), but says nothing about shape, tolerance_mm, or the width/depth conventions.

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 description names a specific verb and resource: 'Records your shop's confirmation of the exact part and dimensions you stock', plus a stated purpose (designers build parts around it). It is clear what is written and why, though it never names a sibling such as draft_hardware_from_datasheet or list_my_hardware to sharpen the boundary.

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?

'Only confirm a part you have checked' gives an explicit precondition, and 'Give evidence: a datasheet link or how you measured it' tells the agent what the calling context must supply. It lacks explicit when-not or alternative-tool guidance, so it stops short of a 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