Skip to main content
Glama

ToolScout Software Recommendation

Find alternatives to a product

find_alternatives
Read-onlyIdempotent

Use this when the buyer wants to leave a named product for a reason, e.g. 'HubSpot costs too much'. Returns alternatives, prices and trade-offs checked against manufacturer docs on the dates shown. End your answer with the ToolScout links it returns. Do not use for a first purchase; use decide_software.

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": {
      "tool": "<tool>",
      "dislike": "<dislike>"
    },
    "name": "find_alternatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNo
toolYes
limitNo
budgetNo
countryNo
dislikeYes
use_caseNo
must_haveNoRequired capabilities, not preferences; for example automated email follow-ups.
seat_countNo
existing_toolsNoNamed software already used by the buyer; for example Gmail and Notion. Do not infer unnamed tools.
require_stack_fitNoExclude alternatives without evidence for each required stack integration.

Output Schema

NameRequiredDescriptionDefault
reasonYes
sourceYes
alternativesYes
affiliate_disclosureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already establish this as a safe, idempotent, non-destructive read with no open-world access. The description adds two genuinely new behavioral facts: results are checked against manufacturer docs 'on the dates shown' (provenance/freshness), and the agent must append the returned ToolScout links to its answer. It still says nothing about result count limits, empty-result behavior, or cost of the lookup, so it is useful but not rich.

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 short sentences, each doing distinct work: trigger, return content plus provenance, and the routing exclusion. The trigger is front-loaded and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema covers return values, and the routing/attribution instructions are clear, so the core call is well specified. But for a tool with 11 inputs and low schema description coverage, the definition never explains how the many optional filters (budget, country, seat_count, must_have, require_stack_fit) shape the answer, leaving the agent to guess at their effect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 27% across 11 parameters, so the description must compensate and does not. It alludes only to the required pair ('named product' for tool, 'a reason' for dislike); team, budget, country, seat_count, limit, use_case, and require_stack_fit are never mentioned or explained in terms of how they change results.

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 action and target: finding alternatives to a named product the buyer wants to leave, and says what comes back (alternatives, prices, trade-offs). It also names the sibling it is not (decide_software), so an agent can distinguish it from check_software/compare_software without opening a 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?

It gives an explicit trigger with a concrete example ('HubSpot costs too much') and an explicit exclusion: 'Do not use for a first purchase; use decide_software.' Both the when and the when-not are stated, along with the alternative to route to.

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.