Skip to main content
Glama

Documented alternatives to a product

get_alternatives
Read-onlyIdempotent

Use this when the user asks what else to consider instead of a named product. Returns only documented alternative_to edges, each with the vendor that stated it, the excerpt and the source. An empty list means we hold no documented alternative - it never means none exist; use search_products with the product's category for candidates.

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": {
      "slug": "<slug>"
    },
    "name": "get_alternatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe product slug.

Output Schema

NameRequiredDescriptionDefault
urlYes
nameYes
slugYes
countYes
contractYes
alternativesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the genuinely non-obvious trust semantics - results are limited to documented edges, and an empty list means no documented alternative is held, never that none exists. That caveat prevents a serious misreading of the output; it stops short of describing provenance ranking or coverage breadth.

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 ordered as trigger, return content, and critical caveat plus fallback. No restatement of the name or title, and every clause carries information an agent needs before calling.

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?

With one required parameter, an output schema, and full annotations, the description covers everything left open: when to reach for it, what the edges contain, and how to interpret an empty result. Nothing an agent needs to call it correctly is missing.

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 100% for the single required 'slug' parameter, so the schema already carries the documentation burden. The description only refers to 'a named product' without adding format, slug-resolution or normalization guidance beyond what the schema states. 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 retrieval: documented alternative_to edges for a named product, each with vendor, excerpt and source. It distinguishes itself from search_products, which is framed as the candidate-discovery path rather than the documented-edge path, so an agent can tell the two apart without opening either schema.

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?

Opens with an explicit triggering condition ('when the user asks what else to consider instead of a named product') and names the alternative (search_products with the product's category) for the case where the user wants candidates rather than documented claims. The when/when-not split is fully spelled out.

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