Skip to main content
Glama

get_ai_consensus_on_topic

Read-only

Use when researching how AI systems characterize a vendor, category, trend, or business topic across multiple platforms simultaneously. Returns consensus score, sentiment mix, key themes, and platform-by-platform breakdown. Example: AI in healthcare scores 0.78 consensus — key themes: clinical decision support, administrative automation, prior auth reduction — high consensus signals established narrative safe for board communications. Source: Stratalize AI citation composite. $0.50 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": {
      "topic": "<topic>"
    },
    "name": "get_ai_consensus_on_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely non-redundant behavior: the exact returned fields (consensus score, sentiment mix, key themes, platform breakdown), the data source (Stratalize AI citation composite), and a per-call cost of $0.50 USDC — a material invocation constraint not present in schema or annotations. It does not cover rate limits, latency, or failure modes.

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?

It is front-loaded with the 'Use when' trigger, then return shape, then an illustrative example, then source and price — a logical order with no filler sentences. The example is longer than strictly necessary but earns its place by showing how to read the consensus score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 does a good job enumerating return fields and adding pricing, which is enough for an agent to decide to call it. The gaps are the undefined 'category' parameter and the absence of any note on payment/auth mechanics for a paid endpoint or on how many platforms are sampled.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden. It implies what 'topic' holds (vendor, category, trend, business topic) but says nothing about the optional 'category' parameter — and worse, 'category' appears in the prose as a kind of topic, creating ambiguity about whether it is the same thing or a separate classifier.

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 pairs a specific verb ('researching how AI systems characterize') with a concrete resource set (vendor, category, trend, business topic) and states the cross-platform scope. It is clearly a consensus/sentiment aggregation tool, distinguishable from siblings like get_category_ai_leaders or get_sector_ai_intelligence, though it never names those alternatives explicitly.

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 researching how AI systems characterize a vendor, category, trend, or business topic across multiple platforms simultaneously' gives a clear triggering context. However, it offers no when-not guidance and does not point to any sibling for adjacent questions (e.g., AI leaders by category vs. consensus), leaving the agent to infer boundaries.

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