Skip to main content
Glama

Scan Competitor AI Presence

scan_competitor_ai_presence
Read-onlyIdempotent

Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our competitors?". Returns ranked list with score, confidence, signal density per entity.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entities": [
        "Pipeworx",
        "Zapier"
      ]
    },
    "name": "scan_competitor_ai_presence"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelsNoWhich models to probe. Supported: "workers-ai" (free default), "anthropic" (requires _apiKey). Omit for just workers-ai.
_apiKeyNoOptional Anthropic API key, only if "anthropic" is in models. Passed to api.anthropic.com per probe.
contextNoOptional shared context applied to every probe (e.g. "B2B SaaS", "Boston restaurant"). Disambiguates common names.
entitiesYesArray of 2-8 entities to compare (brand/business/product names). First entry treated as the "subject" for narrative; rest are competitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Optional Anthropic API key — only if \"anthropic\" is in models. Passed to api.anthropic.com per probe."New value: +"Optional Anthropic API key, only if \"anthropic\" is in models. Passed to api.anthropic.com per probe."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "entities": [
      +      "Pipeworx",
      +      "Zapier"
      +    ]
      +  }
      +]
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds real behavior beyond that — per-entity probing via ai_visibility_check, score-based ranking, and the returned fields (score, confidence, signal density) — but omits the cost/latency implication of probing N entities across multiple models, which matters for an open-world multi-call tool.

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 description front-loads the core purpose ('Compare AI visibility across multiple entities side-by-side') and then justifies it with mechanism, use case, and return shape in three compact sentences. Each sentence carries information, with only the quoted example bordering on decorative.

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?

For a 4-parameter tool with full schema coverage, strong annotations, and no output schema, the description covers purpose, mechanism, use case, and return fields adequately. The only meaningful omission is any indication of probe volume or runtime cost when many entities and multiple models are requested.

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?

Schema description coverage is 100%, so every parameter including models, _apiKey, context, and entities is already documented with its constraints. The description reinforces the entity semantics ('your brand + N competitors') but adds no syntax, limits, or format detail beyond what the schema states, so the baseline of 3 applies.

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 names a specific verb and resource (compare AI visibility across multiple entities) and explains the mechanism: each entity is probed with ai_visibility_check and ranked by score. That clearly separates it from the single-entity ai_visibility_check sibling, though it says nothing about the similarly named compare_entities sibling, leaving one potential source of ambiguity.

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?

It supplies a concrete usage context ('competitive AI-marketing audits: does Claude know about us as well as our competitors?') that tells an agent when this tool is the right fit. It stops short of explicit exclusions or naming the single-entity alternative to use instead, so the routing guidance is clear but not complete.

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.