Skip to main content
Glama

Stratalize Intelligence

Get Ai Consensus On Topic

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

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description adds genuinely non-structural facts: the upstream source ('Stratalize AI citation composite') and the per-call price ('$0.50 USDC per call'), plus a high-level shape of the return payload. It does not mention rate limits or what happens on an unknown topic, so not 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 the usage trigger, then outputs, then a worked example, then provenance and pricing; each block is short. The example sentence carries mild promotional framing ('safe for board communications') but also demonstrates the score format, so it largely earns its place.

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 reasonable job enumerating return fields and gives an example score value that implies a 0–1 range. However, for a two-parameter tool with zero schema documentation, the complete absence of parameter guidance and of any note on cost semantics beyond the unit price leaves real operational gaps.

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% for two parameters, so the description must carry the burden and does not. It lists 'topic' and 'category' only as example subject types in prose, never clarifying that 'category' is a distinct optional parameter or how it interacts with 'topic' — an agent could easily conflate the two.

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 opens with a specific verb and resource ('researching how AI systems characterize a vendor, category, trend, or business topic') and names the output artifact ('consensus score, sentiment mix, key themes, platform-by-platform breakdown'). It is clear what the tool produces, though it does not explicitly contrast itself with near-neighbors like get_sector_ai_intelligence or get_category_disruption_signal.

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... across multiple platforms simultaneously' gives a concrete triggering condition and even an interpretive rule ('high consensus signals established narrative safe for board communications'). There are no explicit when-not conditions or named alternatives, which keeps it short of a 5.

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