Skip to main content
Glama

Storewire Lite demo store

Check whether two products work together

check_compatibility
Read-onlyIdempotent

Whether two Trailhead Supply products work together (product + with), or which products fill a role for one product (product + role: accessory, requires, works_with; up to 8 products on sale, with price and stock). The verdict is listed (the catalogue links the two products), fits_rule (no link, but a catalogue rule matches them; reason says which) or unknown (the catalogue holds no data on the pair; unknown does not mean incompatible).

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": {
      "product": "<product>"
    },
    "name": "check_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoInstead of with: the relation to list products for, e.g. accessory for what fits it, requires for what it needs.
withNoThe second product, named the same ways as product. Give this or role.
localeNoAnswer language: en (default en). Names, labels and URLs follow it.
productYesThe product: its public_id from an earlier answer, its page URL or slug on the store's website, or the manufacturer model number.

Output Schema

NameRequiredDescriptionDefault
withYes
reasonYesWhy, in the answer language.
matchesYesRole mode: the products filling the role, best first; empty in pair mode.
productYes
verdictYes
truncatedNoPresent and true only when the answer outgrew the size budget and its last list items were left out; ask narrower to see them.
answer_typeNoWhat this answer is, for rendering.
relation_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real context beyond them: the three verdict categories and their meanings, that fits_rule carries a reason, the cap of 8 products with price and stock, and the important caveat that 'unknown does not mean incompatible'. It does not mention error handling for an unrecognized product.

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

Conciseness3/5

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

It is front-loaded with the two modes, which is good, but the second and third sentences are long parenthetical chains that take effort to parse. The content mostly earns its place, yet the verdict taxonomy could be tightened rather than nested inside commas.

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 an output schema present, the description need not explain return shapes, and it still usefully interprets the verdict values so the agent won't misread 'unknown' as incompatibility. Missing only edge-case guidance such as behavior when the product identifier resolves to nothing.

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 100% and each parameter already carries a description, so the schema does the heavy lifting. The description reinforces the with/role exclusivity and glosses the enum values, but adds little syntax or format detail the schema lacks; baseline 3 applies.

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 two concrete modes: pairing two named products ('product + with') and enumerating products that fill a relation ('product + role: accessory, requires, works_with'). That is specific enough to separate it from a generic lookup, though it never names a sibling (compare_products, get_product) to contrast against.

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 explicitly says which parameter combination triggers which behavior ('product + with' vs 'product + role'), which is the key routing decision an agent faces. It stops short of exclusions — nothing says when to prefer compare_products or get_product instead, so the agent must infer the boundary.

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.