Skip to main content
Glama
Sign In
Eclipse Bazaar MCP

Eclipse Bazaar MCP

by CYAN-ECLIPSE-TECHNOLOGIES-LLC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Compare Products

compare_products
Read-onlyIdempotent

Compare two or more product IDs side by side to assess status, pricing model, certification verdict and scope, platforms, and categories; use get_product for one product’s full entry.

Instructions

Side-by-side comparison of 2+ product ids: status, pricing model, certification verdict and scope, platforms, categories. Use get_product instead when you need one product's full entry.

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

Input Schema

NameRequiredDescriptionDefault
idsYesTwo or more catalog product ids, as returned by search_products, find_solutions, or list_categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.5
    • addedInput schema / properties / ids / description
      Added value: +"Two or more catalog product ids, as returned by search_products, find_solutions, or list_categories."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing what comes back per product (status, pricing model, certification verdict/scope, platforms, categories), which matters since there is no output schema. Minor gap: nothing said about unknown/invalid ids or mixed-result handling.

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?

Two sentences, zero filler. The comparison scope is front-loaded and the routing hint follows it, which is the right priority order for a reader deciding whether to call.

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?

Complete for a small read-only tool: the compared fields substitute for the absent output schema, and the sibling alternative is given. Only edge-case behavior (fewer than 2 ids, unrecognized id) is left unstated, which is a minor omission rather than a blocker.

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?

There is a single parameter with 100% schema description coverage, and the schema already documents the provenance of ids (search_products, find_solutions, list_categories). The description's '2+' phrasing reinforces but does not extend the schema's meaning, 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?

Specific verb and resource ('Side-by-side comparison of 2+ product ids') plus an enumeration of the exact dimensions compared (status, pricing model, certification verdict and scope, platforms, categories). It also explicitly separates itself from get_product, so an agent can pick between them without opening either schema.

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

Usage Guidelines5/5

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

States the positive case (2+ ids, side-by-side) and names the alternative plus the condition that selects it: 'Use get_product instead when you need one product's full entry.' No inference required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools