Skip to main content
Glama

get_competitive_displacement_signal

Read-only

Use when tracking competitive threats to an incumbent vendor or identifying switching trends in a software category. Returns vendors mentioned as replacements for a target vendor with switch narrative and mention counts. Example: Salesforce displacement — HubSpot replacing in SMB at 28 mentions, Dynamics replacing in enterprise at 19 — highest displacement pressure in mid-market 100-500 employees. Source: Stratalize citation 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>"
    },
    "name": "get_competitive_displacement_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendor_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior beyond them: the payload shape (replacement vendors, switch narrative, mention counts), a concrete worked example, and a $0.10 USDC per-call price. It stops short of describing the analysis window or how mentions are counted, and the example reads like fabricated result data rather than a schema of the response.

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?

Usage guidance is front-loaded and every sentence contributes something (purpose, payload, illustration, source, price). The example sentence is dense and slightly unwieldy with three embedded statistics, but it is not filler.

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 single-parameter, no-output-schema tool with safety annotations already supplied, this covers purpose, return contents and cost. The notable omission is temporal scope — mention counts over what period, and whether recent switches weight more heavily — which an agent would need to interpret results 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?

With one parameter at 0% schema description coverage, the description must carry the burden. It clarifies that vendor_name is the incumbent being displaced rather than the replacement, and the example implies plain vendor names ("Salesforce", "HubSpot") work. It gives no format rules (legal name vs. ticker vs. domain) or case sensitivity, leaving real ambiguity.

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 states a specific verb and resource: it returns vendors mentioned as replacements for a target vendor, along with switch narrative and mention counts. That is far more precise than the sibling get_competitive_landscape_synthesis, though it never names such siblings explicitly to draw the boundary.

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 opens with an explicit use case — tracking competitive threats to an incumbent or identifying switching trends in a software category — which gives the agent a clear trigger condition. It offers no when-not-to-use guidance and does not point to any alternative tool for adjacent questions such as overall category structure.

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