Skip to main content
Glama

The Builders Supply catalog

Compare products

compare_products
Read-onlyIdempotent

Side-by-side attributes, price, availability, dimensions and weight of 2 to 10 SKUs.

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": {
      "skus": "<skus>"
    },
    "name": "compare_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
skusYes2 to 10 store SKUs

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, openWorld=false, so safety is fully covered structurally. The description adds essentially nothing beyond that: it does not say how missing or invalid SKUs are handled, whether rows align by attribute, or how output is ordered.

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?

One short sentence with no filler, and the scope (which attributes, how many SKUs) is front-loaded. The only flaw is that it is a sentence fragment lacking an explicit action verb, which slightly reduces scannability.

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 an output schema present, return values need no explanation, and the tool is a simple single-parameter read. Still, the definition is thin for a comparison tool: nothing about how products that fail lookup are surfaced or what the agent should do with the result.

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 the single parameter already documents '2 to 10 store SKUs'. The description restates the same range without adding format, delimiter, or validation semantics, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence names the resource and the content returned (attributes, price, availability, dimensions, weight) plus a cardinality bound, so an agent can infer it compares SKUs. But it is a noun phrase with no verb, and it never distinguishes itself from siblings like get_product or search_products.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to use this versus get_product (single product) or search_products (find products), and no prerequisites or exclusion conditions. The only implied guidance is the 2-to-10 SKU count, which is a constraint rather than routing guidance.

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