Skip to main content
Glama
Sign In
Eclipse Bazaar MCP

Eclipse Bazaar MCP

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

Get Certification

get_certification
Read-onlyIdempotent

Retrieve a product's Test Bench certification verdict by catalog id, including live scorecard summary, certified scope, and not-tested items; returns NOT YET CERTIFIED when no verdict exists.

Instructions

The latest Test Bench verdict for a product, with a live scorecard summary, the certified scope, and the not_tested list. Returns an explicit NOT YET CERTIFIED answer when no verdict exists. Use get_product instead when you need the full catalog entry 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_certification"
  }
}

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.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description focuses on what matters beyond that: the return shape and the explicit NOT YET CERTIFIED outcome when no verdict exists. It does not cover behavior for an invalid or unknown product id, which keeps it below a 5.

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 that lead with what is returned, then the empty-result behavior, then the sibling routing. No filler and nothing buried at the end.

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?

With no output schema, the description carries the burden of describing the response and does so well: verdict, scorecard summary, certified scope, and not_tested list. Only failure modes such as unknown ids are left unaddressed.

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 id parameter is fully documented there, including its provenance (search_products, find_solutions, list_categories). The description adds no syntax or format detail beyond the schema, so the 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 and resource ("latest Test Bench verdict for a product") plus the payload it returns (scorecard summary, certified scope, not_tested list), and explicitly contrasts itself with get_product so it can't be confused with that sibling.

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?

Names the alternative (get_product) and the exact condition that selects it ("when you need the full catalog entry for the same id"), and flags the NOT YET CERTIFIED path so an agent knows a missing verdict is a normal answer rather than an error.

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