Skip to main content
Glama

get_category_disruption_signal

Read-only

Use when assessing whether a software category faces near-term displacement risk, or timing a market entry or exit decision. Returns disruption risk score from 0 to 1 with evidence strings from citation volume patterns. Example: ERP category — disruption risk score 0.71, evidence: 34 citations referencing AI-native alternatives, 12 referencing no-code replacements — HIGH disruption risk for legacy on-premise vendors. Source: Stratalize citation volume heuristics. $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": {
      "category": "<category>"
    },
    "name": "get_category_disruption_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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, open-world), and the description adds real context beyond them: the 0–1 score scale, evidence strings from citation volume patterns, the underlying heuristic source, and a per-call cost of $0.10 USDC. It does not disclose limitations such as behavior for unknown/ambiguous categories or data freshness, which keeps 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-loaded with usage, then return behavior, then a concrete worked example, then provenance and price. Every element earns its place, though the ERP example is lengthy and could be trimmed without losing much.

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 one simple parameter, no output schema, and no nested objects, the description supplies the missing pieces: what the return value looks like, where the signal comes from, and what it costs. Only marginal gaps remain (input format, edge-case behavior), which is appropriate for a low-complexity read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage on the single required 'category' parameter, so the description must carry it. It does add meaning—'category' is a software category (e.g. ERP) whose citation patterns are analyzed—but it does not specify accepted format (free text vs. canonical slug) or how matching failures are handled.

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+resource: returns a disruption risk score (0–1) for a software category, with citation evidence. It implicitly distinguishes category-level displacement from the vendor-level siblings (get_vendor_risk_signal, get_competitive_displacement_signal) by scoping to 'a software category', but never names those siblings, so an agent must infer 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?

Gives explicit triggering context: 'Use when assessing whether a software category faces near-term displacement risk, or timing a market entry or exit decision.' Clear when-to-use, but no when-not-to-use and no explicit routing to the closest alternative (get_competitive_displacement_signal).

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