Skip to main content
Glama

Recommend a blind

get_product_recommendation
Read-only

Translate a customer's primary concern into a product recommendation. primary_concern must be one of: blockout, heat, glare, moisture, privacy, security, automation. Optionally narrow by room (bedroom, lounge, etc.), location, budget, and aesthetic. Returns a recommended product_id with rationale, pass it to get_price or configure_product next. For security there is no shop product: it returns a hand-off to our security shutters page (installed in the Garden Route only).

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": {
      "primary_concern": "<primary_concern>"
    },
    "name": "get_product_recommendation"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomNo
locationNo
aestheticNo
max_budget_zarNo
primary_concernYes

Output Schema

NameRequiredDescriptionDefault
notesNo
handoffNo
recommendationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the return shape (recommended product_id with rationale) and the fact that one enum value exits the catalog entirely into a regional hand-off. It does not mention confidence, tie-breaking, or what happens when budget/aesthetic conflict with the concern.

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?

Front-loaded with the core action, then the enum constraint, then optional narrowing, then next steps and the exception. Dense and mostly waste-free, though restating all seven enum values duplicates the schema and costs a full clause.

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?

An output schema exists, so return values needn't be spelled out, yet the description still signals product_id plus rationale. For a 5-param, single-required-param recommendation tool with a real exception path, an agent has enough to call it correctly; only the ambiguous optional filters leave a gap.

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 description coverage is 0%, so the description must carry the load, and it does explain the meaning of the required 'primary_concern' and maps budget/aesthetic/room/location to the optional narrowing params. However 'location' and 'aesthetic' remain undefined (city? window orientation? style vocabulary?) and the enum list merely repeats the schema, so it only partially compensates for the coverage gap.

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 transformation: convert a customer's 'primary_concern' into a 'product recommendation', and explicitly scopes the remedy to the seven concern categories. It is clearly distinguishable from siblings like get_price or configure_product, which the description names as downstream steps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit sequencing guidance ('pass it to get_price or configure_product next') and covers a non-obvious edge case: for 'security' there is no shop product, so it returns a hand-off to the shutters page limited to the Garden Route. It does not say when to prefer this over search_catalog/lookup_catalog for product discovery, so the alternative routing is only partially addressed.

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