Skip to main content
Glama
Sign In
Eclipse Bazaar MCP

Eclipse Bazaar MCP

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

Get Product

get_product
Read-onlyIdempotent

Retrieve the full catalog entry for a product ID, covering capabilities, pricing, platforms, certification scope, untested areas, live status, and install-plan availability.

Instructions

Full catalog entry for one product id: capabilities, problem statements, pricing model, platforms, tools, and the certification block including what was NOT tested, plus the product's live_state_note and its explicit install_plan status (no install plan exists yet). Use get_certification instead when you only need the bench verdict, scope, and not_tested list for the same id.

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": {
      "id": "<id>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCatalog product id, 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 / id / description
      Added value: +"Catalog product id, as returned by search_products, find_solutions, or list_categories."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety adds nothing. The description does add real behavioral context: it discloses that the certification block includes what was NOT tested, that live_state_note is present, and that no install plan exists yet — preventing the agent from expecting an install plan. It does not cover error behavior for an unknown id, so it stops short of full disclosure.

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?

Two sentences, front-loaded with the payload contents and back-loaded with the routing rule to the sibling. The dense mid-sentence field list is slightly run-on but every item is informative, and nothing is redundant with the title.

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 burden of telling the agent what comes back, and it does so by enumerating the returned blocks and flagging the empty install_plan state. Combined with the sibling routing hint, an agent has enough to call this correctly; only invalid-id behavior is unstated, a minor omission.

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 required param with 100% schema description coverage, which already tells the agent where ids come from (search_products, find_solutions, list_categories). The description only restates "one product id" and adds no format, casing, or validation detail beyond the schema, 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+resource ("Full catalog entry for one product id") followed by an enumeration of the exact blocks returned: capabilities, problem statements, pricing model, platforms, tools, certification, live_state_note, install_plan. It explicitly positions itself against get_certification, so an agent can distinguish it from siblings without opening a 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?

The final sentence names the alternative tool (get_certification) and the precise condition that selects it (when you only need bench verdict, scope, and not_tested). That is an explicit when-to-use-vs-alternative rule, not an implied one.

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