Skip to main content
Glama

findCompatibleParts

Find FitsThis maintenance kits/filters compatible with a device model. Returns fit_status, evidence, USD price (+ optional shipping estimate / local approx when shipToCountry set), seller rating, ETA. Follow with getProduct + getReviews before recommending purchase.

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

Input Schema

NameRequiredDescriptionDefault
needNoe.g. filter, dust bag, 3-month kit
deviceQueryNo
deviceModelIdNo
shipToCountryNoISO country e.g. AU, US — soft shipping + local approx when set

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / shipToCountry
      Added value: +{
      +  "description": "ISO country e.g. AU, US — soft shipping + local approx when set",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it enumerates the return payload (fit_status, evidence, USD price, seller rating, ETA) and discloses conditional behavior — shipping estimate and local approximation only appear when shipToCountry is set. It does not cover permissions, rate limits, or what 'evidence' actually contains, leaving some behavioral gaps for a tool with zero annotation coverage.

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 sentences, all load-bearing: purpose first, return contents second, downstream workflow third. No filler, no restatement of the tool name, and the most important qualifying detail (shipToCountry conditioning the shipping fields) is embedded efficiently.

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 4-parameter read tool with no annotations and no output schema, the description covers what the agent most needs: what comes back and what to do next. The remaining gap is input selection (deviceQuery vs deviceModelId, and whether need is required when deviceModelId is supplied), which matters for correct invocation.

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

Parameters2/5

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

Schema coverage is only 50%, and the description restates only the shipToCountry conditional, which the schema already documents. The most consequential ambiguity — whether deviceQuery and deviceModelId are alternatives, and which to prefer — is clarified in neither the schema nor the description, and the role of 'need' (optional? required? affects matching?) is likewise unexplained.

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 states a specific verb and resource: finding maintenance kits/filters compatible with a device model, plus the fit-check framing (fit_status, evidence) that distinguishes it from a generic product search. It does not explicitly contrast itself with searchProducts or identifyDevice, so the differentiation is implied rather than stated.

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?

It gives a clear workflow rule: follow with getProduct and getReviews before recommending a purchase, which tells the agent this is a mid-pipeline tool rather than a terminal one. It gives no when-not-to-use guidance and no advice on choosing between deviceQuery and deviceModelId, so exclusions and input-selection guidance are absent.

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