Skip to main content
Glama

Compare exact Nexez offers

nexez_compare_offers
Read-only

Compare 2-5 exact published offers by listing slug and offer key. Returns published price, currency, availability, configuration, seller facts, and per-item errors. Preserves currencies and price text without currency conversion or declaring a cheapest option. Does not validate checkout or hold inventory.

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": {
      "offers": "<offers>"
    },
    "name": "nexez_compare_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
offersYesTwo to five distinct exact offers previously returned by discovery, each identified by listing slug and offer key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, non-destructive, open-world behavior, and the description adds substantial context beyond them: the exact return payload (price, currency, availability, configuration, seller facts, per-item errors), the no-conversion/no-cheapest-option guarantee, and the explicit non-behaviors. Per-item error reporting is especially valuable for a batch comparison call with no output schema.

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 tight sentences: what it does and with what inputs first, then what comes back, then the guarantees and non-behaviors. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so by enumerating result fields and error granularity. Combined with annotations covering the safety profile and a fully documented schema, an agent has everything needed to call it correctly and interpret results.

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 nested slug/offer descriptions already define both fields precisely, including the 'not a URL' caveat and the services-0 example. The description only restates 'listing slug and offer key' and the 2-5 bound, adding no format or syntax detail the schema lacks, so baseline 3 applies.

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

Purpose5/5

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

States a specific verb (compare) and resource (2-5 exact published offers), names the identifying inputs (listing slug and offer key), and summarizes the returned fields. It also implicitly separates itself from the validation siblings by stating it does not validate checkout or hold inventory.

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?

Explicitly scopes the tool to 2-5 exact offers previously returned by discovery and rules out checkout validation and inventory holding. It never names a concrete sibling to use instead for those tasks, so the alternative routing is inferred rather than stated.

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