Skip to main content
Glama

Pocket size for a part

preview_hardware_pocket
Read-onlyIdempotent

The exact openings Printlooper would cut for a confirmed part at given fit settings, before a design is made around it.

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": {
      "hardware_revision_id": "<hardware_revision_id>"
    },
    "name": "preview_hardware_pocket"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many of this part
mountNopocket keeps a floor under the part; through passes straight through a panelpocket
columnsNoParts per row along X. Must divide the count. Default is one row.
pitch_mmNoCentre-to-centre spacing. Required for more than one part.
plate_mmNoPanel thickness for a through cutout. Through only.
taper_mmNoEntry chamfer that helps the part go in. Pockets only.
clearance_mmNoGap per side around the part
floor_hole_mmNoRound hole through each pocket floor, for a screw or shaft. Pockets only.
hardware_revision_idYesrevision_id from list_available_hardware

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description still adds that this is a dry-run preview producing cut geometry rather than creating anything, which reinforces the no-side-effect contract. It does not describe what the returned geometry looks like or how it is formatted in the case of error conditions.

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?

A single sentence with the core purpose and the pre-design scope stated up front, and no restatement of the title or schema. Nothing could be cut without losing information.

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?

With nine parameters, an enum mount mode, and no output schema, the description carries a lot of weight — yet it never says what a 'preview' returns (a shape, measurements, a rendered file) or how the agent should present it. It also leaves the relationship to list_available_hardware (source of hardware_revision_id) implicit. Adequate, but there are clear gaps for a geometry-computing tool.

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 parameter is already documented in the schema, setting the baseline at 3. The description contributes only the framing 'fit settings' and confirmation that a revision of a part is the input; it adds no detail on how count/columns/pitch combine, which lives in the schema descriptions.

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?

Names a specific resource and output: the exact cut openings for a confirmed hardware part at given fit settings, plus the scope qualifier that no design exists yet. This is clearly distinguishable from a listing/pricing tool. It stops short of naming the sibling it differs from (e.g. confirm_hardware_dimensions), so it earns a 4 rather than 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 phrase 'before a design is made around it' implies the intended moment of use — checking clearances prior to modelling — but no explicit when-to-use rule, prerequisite (a confirmed part), or when-not guidance is stated. An agent must infer the trigger condition from context.

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