Skip to main content
Glama

compatsy 3D printing

Compare products

compare
Read-onlyIdempotent

Side-by-side spec table with offers and the fields that differ. Pass 2-10 product_ids, or a category with filters. Example: {"product_ids":["prusa-core-one","bambu-lab-p1s"]}

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

Input Schema

NameRequiredDescriptionDefault
limitNo
filtersNoNeeds category. Spec field -> exact value, e.g. {"material":"brass"}; an unknown field or value is an error listing the valid ones
categoryNo
product_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description's added value is the output shape: a spec table with offers and a highlighted set of differing fields. That is real behavioral context, especially with no output schema. It omits error behavior for oversized ID lists or invalid category+filters combinations, which keeps it below 5.

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

Conciseness4/5

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

Three short front-loaded clauses plus a compact inline example; nothing is padded. The example is useful for illustrating ID formatting, though it partially duplicates what the schema already constrains.

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 tool with a nested filters object, no output schema, and an undocumented 'limit' parameter, the description leaves real gaps: no return size or pagination behavior, no note on what happens when filters match nothing, and no guidance on choosing between the two input modes. The stated output shape does cover the most important missing piece.

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 only 25%, so the description must carry more weight. It correctly signals the two mutually exclusive input modes (ids array vs category+filter object) and shows the ID format by example, but the 2-10 bound merely repeats minItems/maxItems, and the 'limit' parameter is never explained in the description or the schema.

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 concrete verb and resource ('side-by-side spec table with offers and the fields that differ') and says what it compares. It is clearly distinct from get_product and search_products in intent, but it never names those siblings, so the differentiation is inferred 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives two invocation modes ('Pass 2-10 product_ids, or a category with filters') plus a worked example, which implies when to use it. It does not say when to prefer get_product or search_products instead, nor what happens if both product_ids and category are supplied.

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.