Skip to main content
Glama
Sign In
Eclipse Bazaar MCP

Eclipse Bazaar MCP

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

List Categories

list_categories
Read-onlyIdempotent

Retrieve catalog categories with product counts by status and product IDs. Use the results to browse products, fetch certifications, or filter product searches by category.

Instructions

All catalog categories with product counts broken down by status (live / first-party / in-development / spec), plus the product ids in each category. Start here to browse the catalog; use the returned ids with get_product or get_certification, and the category names as search_products' category filter.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description's job is to add context — which it does by disclosing the full return structure (status breakdown counts plus id lists). It does not mention result size or whether the listing is exhaustive/unpaginated, which would matter for a zero-parameter full-catalog call.

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 dense sentences with zero filler: the first defines output, the second defines workflow and downstream usage. Both are front-loaded with the actionable information.

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?

There is no output schema, so the description carries the burden of describing returns — and it does, naming the four status buckets and the included product ids. For a zero-parameter, read-only discovery tool, an agent has everything needed to call it and use the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline is 4. The description correctly implies an unfiltered, complete listing consistent with the empty schema.

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+resource ('All catalog categories') and immediately specifies the payload shape: product counts broken down by live/first-party/in-development/spec status plus product ids per category. This is clearly distinct from siblings like search_products or get_product, which return products rather than the category taxonomy.

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?

Gives an explicit entry-point recommendation ('Start here to browse the catalog') and concrete downstream routing: returned ids feed get_product or get_certification, and category names feed search_products' category filter. Both the when-to-use and the alternative-tool relationship are spelled out.

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