Eclipse Bazaar MCP

Find Solutions

find_solutions

Read-onlyIdempotent

Describe a problem in plain language to get ranked product matches with fit explanations, status, and certification badges, including clear labels for spec-stage or uncertified products.

Instructions

Describe a problem in plain language; get ranked products with a fit explanation, status, and certification badge inline. Spec-stage products are labelled spec-stage, uncertified products say so. Use search_products instead when you already have keywords or a category in mind; use get_product once you have a product 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": {
      "problem": "<problem>"
    },
    "name": "find_solutions"
  }
}

Input Schema

Name	Required	Description	Default
`problem`	Yes	The problem to solve, in plain language — a sentence or two works best.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.5Nov 6, 2026
- addedInput schema / properties / problem / description
```
Added value: +"The problem to solve, in plain language — a sentence or two works best."
```
First observedv0.1.0Oct 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds valuable return-behavior context beyond annotations: results are ranked, include a fit explanation, status, and certification badge, and explicitly label spec-stage and uncertified products. It does not discuss pagination or result limits, but that is a minor gap given the strong output description.

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 sentences with no waste. The primary action and return value are front-loaded, followed by labeling behavior and then routing alternatives, which is an effective order.

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?

For a single-parameter, read-only tool with no output schema, the description is complete. It covers purpose, expected input style, return content and labeling, and how to route to sibling tools. An agent has everything needed to select and invoke it correctly.

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 parameter 'problem' is fully documented in the schema as a plain-language problem description. The description reinforces this ('Describe a problem in plain language') but adds no new syntax, format, or constraint details beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource: describe a problem in plain language to get ranked products with a fit explanation, status, and certification badge. It clearly distinguishes this tool from search_products and get_product by naming them as alternatives.

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?

It gives explicit when-to-use guidance ('Describe a problem in plain language') and when-not-to-use guidance with named alternatives: use search_products when you have keywords or a category, and get_product once you have a product id. This leaves no ambiguity about routing.

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

Deploy Server