Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the probing mechanism, that each entity is probed separately across models, and the shape of the return ('ranked list with score, confidence, signal density per entity'). It omits cost/latency implications of running N probes and any failure modes when a model is unavailable.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the core comparison behavior and followed by the motivating use case and the return shape. The ranking idea is mentioned twice (sentence one and sentence three), but the second mention adds the concrete output fields.

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 four-parameter tool with no annotations and no output schema, the description covers what it does, why you would call it, and what comes back. Remaining gaps are secondary: no mention of the practical cost of multi-entity, multi-model probing or how partial failures are reported.

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 model options, the _apiKey requirement, and the shared-context disambiguator. The description adds only the framing that the first entity is the 'subject' and the rest are competitors, which the schema already states. Baseline 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?

States a specific verb and resource: compares AI visibility across entities, probing each with ai_visibility_check and ranking by score. By naming the single-entity probe as the mechanism, it implicitly separates itself from a one-entity check. It stops short of explicitly naming a sibling alternative to use instead, so it lands just below the top mark.

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?

Provides a concrete usage context ('competitive AI-marketing audits') and a sample question an agent can pattern-match against ('does Claude know about us as well as our competitors?'). It does not state when NOT to use it, e.g. for single-entity checks or when no Anthropic key is available.

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.