Skip to main content
Glama

get_vendor_alternatives

Read-only

Use when evaluating a vendor switch or building a competitive RFP against an incumbent. Returns alternative vendors with migration complexity scores, estimated savings, and switching narrative. Example: Salesforce alternatives — HubSpot at 22% lower median spend with comparable CRM coverage, Pipedrive at 41% lower for sales-only — migration complexity rated MEDIUM for both. Source: Stratalize competitive displacement composite. $0.10 USDC per call.

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": {
      "vendor_name": "<vendor_name>",
      "reason": "<reason>"
    },
    "name": "get_vendor_alternatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesPrimary driver for evaluating alternatives
vendor_nameYesIncumbent vendor name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld). The description adds material context beyond them: the data source ('Stratalize competitive displacement composite') and a per-call cost of $0.10 USDC. It stops short of describing latency or result-count bounds, keeping it from a 5.

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-loads the when-to-use clause, then returns, then exactly one illustrative example, then source and pricing. Efficient overall, though the example sentence is on the long side relative to the rest.

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 no output schema, the description carries the return-shape burden and does so by naming the fields returned (migration complexity, savings, narrative plus a concrete example). Combined with annotations handling safety and the cost disclosed, an agent has everything needed to call it correctly.

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 coverage is 100% and both parameters are fully documented, so the baseline is 3. The worked example implicitly shows vendor_name ('Salesforce') and a cost-driven reason in action, but adds no format or meaning beyond the schema.

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 verb and resource: 'Returns alternative vendors with migration complexity scores, estimated savings, and switching narrative.' This concretely distinguishes it from sibling tools like get_vendor_benchmark or get_vendor_negotiation_intelligence, which address different questions.

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 when-to-use triggers: 'evaluating a vendor switch or building a competitive RFP against an incumbent.' Clear context, but it names no when-not conditions and no specific alternative sibling to reach for instead.

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