Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Share of voice in AI answers

webops_ai_competitors
Read-onlyIdempotent

The website's share of voice in AI assistants' answers against the counted competitors, and suggested competitors. Another organization's or an unconnected site answers not found. Read-only.

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": {
      "domain": "<domain>"
    },
    "name": "webops_ai_competitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read-only' adds nothing. The one genuinely new behavioral fact is that other organizations' or unconnected sites return no answers, which usefully sets expectations about empty results, but nothing is said about how share of voice is computed or refreshed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the first sentence is syntactically muddled ('against the counted competitors, and suggested competitors') and the read-only trailer is redundant with annotations, so some words fail to earn their 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?

For a one-parameter, closed-world read tool with no output schema, the minimum is present, but it omits the meaning/format of the sole parameter and does not clarify the return shape (e.g., whether suggested competitors are listed separately).

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?

There is a single required 'domain' parameter with 0% schema description coverage, so the description carries the full burden — yet it only says 'the website's', never stating that 'domain' is the site to analyze, its accepted format, or whether it must be a connected site.

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 metric and scope: the site's share of voice in AI assistants' answers versus counted and suggested competitors. It conveys what the tool returns, though the phrasing is garbled and it never explicitly contrasts with webops_ai_visibility or webops_competitors.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance and no named alternatives among the many AI-related siblings (webops_ai_visibility, webops_run_ai_check, etc.). The only constraint-like sentence ('Another organization's or an unconnected site answers not found') describes a data limitation, not when to pick this tool.

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