Skip to main content
Glama

compatsy home espresso

Check fit

check_fit
Read-onlyIdempotent

Does this part fit that machine? Returns a verdict with the rule id and version that decided it, or the missing fields. Example: {"subject_id":"lucca-puck-screen-58mm","target_id":"breville-barista-express"}

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": {
      "subject_id": "<subject_id>",
      "target_id": "<target_id>"
    },
    "name": "check_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_idYesId or slug of the machine the part goes on
subject_idYesPart id or slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / target_id / description
      Previous value: -"Printer or hotend id or slug"New value: +"Id or slug of the machine the part goes on"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the description's job is to add return-shape context, and it does: a verdict plus the rule id and version that decided it, or the missing fields. That is genuinely useful since there is no output schema. It stops short of explaining failure modes for unrecognized ids or what 'missing fields' looks like.

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 compact sentences: the core question first, the return contract second, a concrete example last. No filler and nothing important buried.

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?

For a simple two-parameter read-only tool with no output schema, the description covers purpose, identifier format and return semantics. Gaps are minor: unknown-id behavior and how 'missing fields' is surfaced are left to inference.

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 already 100%, so the schema carries the parameter documentation. The description nevertheless adds value by showing the expected identifier format through concrete slugs ('lucca-puck-screen-58mm', 'breville-barista-express'), which tells the agent the params accept slugs, not just opaque ids.

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 evaluation (does this part fit that machine) plus the return payload (verdict, deciding rule id and version). That clearly separates it from check_stock, get_product, search_products and report_issue. It does not explicitly rule out overlap with the more generic 'compare' sibling, so it falls just short of 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 use case is implied by the question framing: call it when you need a compatibility answer for a part/machine pair. There is no explicit when-not guidance, no statement about what to do if ids are unknown or ambiguous, and no mention of choosing between this and 'compare'.

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.