Skip to main content
Glama

ToolScout Software Recommendation

Check facts about named software

check_software
Read-onlyIdempotent

Use this when the buyer asks about 1 to 5 named products: plan prices, free plan, AI or MCP support, integrations with tools in use, or recent changes, e.g. 'Does Pipedrive work with Gmail?'. Facts are checked against manufacturer docs on the dates shown. Do not use for setup or choosing 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": "check_software"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolsYesProduct names or ToolScout slugs.
budgetNoUse free when only Free-plan integrations count.
seat_countNoPaid seats, to show team price subtotals.
existing_toolsNoSoftware the buyer already uses, to check named integrations; for example Gmail and Notion.

Output Schema

NameRequiredDescriptionDefault
toolsYes
changesYes
missingYes
affiliate_disclosureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is settled. The description adds genuinely new context beyond that: results are sourced from manufacturer documentation and stamped with the dates on which facts were checked, which tells the agent to treat output as time-bound. It stops short of addressing latency or what happens when a lookup has no answer.

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?

Three tight sentences lead with the triggering condition, then broaden the fact categories, then close with the exclusion. The example query and the documentation-source clause both earn their space; only the slightly dense comma-separated fact list slows a first read.

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?

With an output schema present, return values need no explanation, and all four parameters are documented in the schema. The description covers scope, sourcing, and exclusions; the only real gap is that it never says a request exceeding five products must be split across calls, which an agent could miss from maxItems alone.

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%, so the schema already documents all four parameters, including the budget enum semantics and the seat subtotal behavior. The description lightly links facts to parameters ('free plan', 'integrations with tools in use') but adds no syntax or formatting guidance beyond the schema, so the baseline 3 applies.

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 ('check facts') with a clearly enumerated resource scope: prices, free plan, AI/MCP support, integrations, recent changes, limited to 1-5 named products. The exclusion 'Do not use for setup or choosing products' implicitly carves out decide_software, but siblings compare_software and find_alternatives are never named, so the boundary is only partially drawn.

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?

Explicit when-to-use is given with a concrete trigger ('when the buyer asks about 1 to 5 named products') plus a worked example question, and an explicit when-not clause excludes setup and product selection. Alternatives are not named, so an agent must still infer which sibling handles comparison or recommendation requests.

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.