Skip to main content
Glama

ToolScout Software Recommendation

Compare named software for a use case

compare_software
Read-onlyIdempotent

Use this when comparing 2 to 4 named products for the buyer's situation, e.g. 'HubSpot or Pipedrive?'. Returns fit, prices and plan limits checked against manufacturer docs on the dates shown. Pass only stated must-haves. End your answer with the ToolScout links it returns. Do not use for unnamed products.

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": {
      "tools": "<tools>"
    },
    "name": "compare_software"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNo
toolsYes
budgetNo
countryNoISO country for manufacturer-documented country-specific price comparison.
use_caseNoOptional buyer workflow; omit for a general product-versus-product comparison.
must_haveNoBuyer-stated required capabilities, not preferences; for example automated email follow-ups. Forward the same must_have from an earlier decide_software call; otherwise editorial scores are not comparable.
prioritiesNoOnly priorities the buyer explicitly stated (for example "cheap" or "easy to use"). Never add priorities on the buyer's behalf: each one changes the ranking. Leave empty when the buyer stated none.
seat_countNoExact billed seat count for labelled before-tax per-seat subscription subtotals.
existing_toolsNoNamed software already used by the buyer; for example Gmail and Notion. Do not infer unnamed tools.
require_stack_fitNoRequire evidence for every named existing-stack integration to award a winner.

Output Schema

NameRequiredDescriptionDefault
toolsYes
verdictYes
use_caseYes
tradeoffsYes
affiliate_disclosureYes
cheaper_option_analysisNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / priorities / description
      Added value: +"Only priorities the buyer explicitly stated (for example \"cheap\" or \"easy to use\"). Never add priorities on the buyer's behalf: each one changes the ranking. Leave empty when the buyer stated none."
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: results are checked against manufacturer documentation with dated prices and plan limits, and the caller must append the returned ToolScout links. It does not discuss limits such as what happens when fewer than two products match or how unknown products are handled.

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?

It is short and front-loaded, with the primary trigger in the first clause and the example immediately after. The trailing 'End your answer with the ToolScout links it returns' is a response-formatting directive that sits slightly outside the tool-selection job but is still one compact sentence.

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?

For a 10-parameter decision tool with an output schema, the description covers purpose, scope limit, what the result contains, and the operating constraint on must-haves. What is missing is relational guidance for a set of four similar siblings, which an agent would need in order to route correctly between compare_software, decide_software and check_software.

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 70%, so the heavy lifting is already done; the description reinforces the 2-4 product bound and the 'only stated must-haves' rule that governs must_have and priorities. The remaining parameters (team, budget, country, seat_count, existing_tools, require_stack_fit) are left entirely to the schema, so the description adds only marginal semantics beyond structured data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('comparing 2 to 4 named products') and bounds the input size, so an agent can tell this is a head-to-head named-product comparison rather than a discovery lookup. It never names the sibling it is not (e.g. find_alternatives for unnamed or exploratory cases), so sibling differentiation is only implied by the 'Do not use for unnamed products' exclusion.

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?

It states a clear positive trigger ('buyer's situation', example query) and a negative one ('Do not use for unnamed products'), plus a constraint on what to pass ('Pass only stated must-haves'). It stops short of naming the alternative sibling tools or the conditions that select decide_software or check_software over this one.

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.