Skip to main content
Glama

get_platform_divergence

Read-only

Use when identifying gaps between AI platform recommendations and actual market position for a vendor or topic. Returns platform agreement score showing consistency across AI platforms. Example: Salesforce scores 0.91 agreement across ChatGPT, Claude, Gemini, Perplexity — near-universal consensus. Niche vendors often score below 0.50 — high divergence signals a content gap opportunity. Source: Stratalize multi-platform citation composite. $0.02 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": {
      "brand_name": "<brand_name>"
    },
    "name": "get_platform_divergence"
  }
}

Input Schema

NameRequiredDescriptionDefault
brand_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive, open-world), and the description adds value well beyond them: the score is on a 0-1 scale with interpretation anchors (0.91 = near-universal consensus, below 0.50 = divergence), the data source is named, and the per-call cost of $0.02 USDC is disclosed — a genuinely useful detail for an agent deciding whether to call.

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 definition is front-loaded with the usage trigger, then the return value, then a worked example, then provenance and cost. Every element serves a purpose, though the example sentence is slightly longer than needed to convey the threshold interpretation.

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 correctly takes on the burden of explaining the return value and its scale, which it does. The remaining gap is minor: it never clarifies what the 'actual market position' half of the comparison is derived from, so an agent cannot fully predict the response contents.

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?

There is a single parameter (brand_name) with 0% schema description coverage, so the schema contributes nothing. The description only indirectly clarifies it by saying the score is computed 'for a vendor or topic,' which loosely maps to brand_name but does not state accepted formats (company name vs. ticker vs. topic phrase).

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: identifying gaps between AI platform recommendations and a vendor's actual market position, plus a concrete return value (platform agreement score). It does not, however, differentiate itself from the close sibling get_ai_consensus_on_topic, which an agent could easily confuse with this tool.

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?

The opening 'Use when identifying gaps...' gives a clear triggering context, and the niche-vendor example clarifies the scenario further. There are no explicit exclusions or named alternatives, so the agent gets positive guidance but no routing rules away from similar tools.

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