Skip to main content
Glama

Stratalize Intelligence

Get Competitive Displacement Signal

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. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, open-world, non-destructive behavior, and the description adds value on top: it names the data source ('Stratalize citation displacement composite') and discloses a per-call price ($0.10 USDC). That cost and provenance context is exactly what annotations cannot convey, though nothing is said about rate limits or result freshness.

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?

The usage condition is front-loaded, followed by the return shape, then a worked example and pricing. The Salesforce example is somewhat long (mention counts, segment sizes, employee bands) but it usefully demonstrates the output shape, so most of it earns its place.

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 no output schema, the description takes on the burden of describing returns, and it does: replacement vendors, switch narrative, mention counts, plus a concrete example and cost. Remaining gaps are minor — no error/empty-result behavior and no guidance on interpreting the mention counts.

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?

The schema documents vendor_name at 0% coverage, so the description must carry the meaning. It does clarify the crucial semantic role — the vendor is the incumbent being displaced, not the challenger — but gives no guidance on name format, aliases, or whether exact/ticker matching is required.

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?

States a specific verb and resource: 'Returns vendors mentioned as replacements for a target vendor with switch narrative and mention counts.' The framing of 'displacement' (who is replacing whom) is distinct enough from siblings like get_competitive_landscape_synthesis or get_vendor_risk_signal, though no sibling is named explicitly to sharpen the contrast.

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?

'Use when tracking competitive threats to an incumbent vendor or identifying switching trends in a software category' gives a clear triggering context. It does not state when NOT to use it or point to the neighboring signal tools an agent might confuse it with, so it stops short of full routing guidance.

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