Skip to main content
Glama

NS Pros MCP Gateway

nist-standards__scan_competitor_ai_presence

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": "nist-standards__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. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does reasonably well: it discloses the fan-out behavior (one probe per entity per model), the ranking outcome, and the shape of the return ('ranked list with score, confidence, signal density per entity') despite no output schema. It stops short of stating cost/latency implications of N entities × M models or failure behavior when an entity is unrecognized.

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?

Three sentences, front-loaded with the action, then use case, then return shape. Mostly efficient, though 'side-by-side' and 'ranks by score' partially overlap and the example quote is decorative rather than informative.

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?

Covers purpose, mechanism, use case, and return values for a 4-parameter tool with no annotations and no output schema. Missing pieces are mostly operational (cost of probing multiple models, behavior on ambiguous or unknown entity names), which keeps it just under fully complete.

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 all four parameters are already documented, including the 'first entry is subject' convention. The description only restates the entity fan-out ('your brand + N competitors') and adds no syntax, ordering, or model-selection detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: compares AI visibility across multiple entities side-by-side, and explains the mechanism ('Probes each entity ... with ai_visibility_check, ranks by score'). The distinction from a single-entity probe is implicit in 'multiple entities' and 'your brand + N competitors', so an agent can tell what this does without opening the schema.

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?

Gives a clear usage context ('competitive AI-marketing audits: "does Claude know about us as well as our competitors?"') with a concrete example question. It does not explicitly say when NOT to use it or name the single-entity ai_visibility_check as the alternative for one probe, so it falls short of full when/when-not routing.

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.