Skip to main content
Glama

Rank products against requirements

recommend_products
Read-onlyIdempotent

Use this when the user states requirements (budget, weight, must-have features) and wants a ranked shortlist. Without a profile it lists the published finder profiles and their inputs; with a profile it ranks products with published weights, showing every contribution with its evidence. A criterion we could not measure never counts against a product: such products appear under not_enough_data, and only a documented failure rules a product out. For a free-text question use search_products instead.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many ranked products to return.
inputsNoThe profile's inputs by key, e.g. {"budget": 1200, "max_weight_kg": 1.4}. Out-of-range values are clamped and reported, not rejected.
profileNoA finder profile key, e.g. "portable-laptop". Omit to get the list of profiles first.

Output Schema

NameRequiredDescriptionDefault
inputsNo
rankedNo
clampedNo
profileNo
web_urlNo
contractYes
profilesNo
ruled_outNo
consideredNo
ranked_totalNo
not_enough_dataNo
ruled_out_totalNo
not_enough_data_totalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description still adds meaningful behavior beyond that: ranking uses published weights, every contribution is shown with its evidence, unmeasurable criteria never penalize a product but surface it under not_enough_data, and only a documented failure excludes a product. That is real disclosure of scoring and edge-case semantics.

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?

Four sentences, front-loaded with the trigger, then the two modes, then the fairness rule, then the alternative. Nothing is repeated from the title and no sentence could be removed without losing a decision-relevant fact.

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 three-parameter, no-required-parameter tool with an output schema, this covers everything an agent needs to choose and invoke it: when to call, the prerequisite discovery call, how inputs bind to a profile, and how unmeasurable criteria are handled. Return shape is left to the output schema, 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%, so the baseline applies; the description does add the mode semantics of 'profile' (omit it to get the list of profiles first) and frames 'inputs' as keyed to the chosen profile. The clamping behavior it mentions is already stated in the schema, so the net gain over structured fields is modest.

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 (rank products against stated requirements) and immediately splits the tool into its two concrete modes: listing finder profiles when no profile is given, and ranking products when one is. The sibling it is not (search_products) is named, so an agent can separate this from free-text search without inspecting schemas.

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 trigger (user states budget, weight, must-have features and wants a ranked shortlist) and an explicit exclusion with the alternative to use instead (free-text question → search_products). The profile-less case is also routed: call without a profile to discover profiles and their inputs first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources