Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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

A3.9/5.0
Behavior3/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 disclose the fan-out mechanism (one probe per entity, possibly across multiple models) and the ranking behavior, which is genuinely useful context beyond the schema. However, it omits operational consequences of that fan-out: probe count, latency, failure handling if one entity errors, and rate limits — all material for a tool that issues N×M external API calls.

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 core action, then mechanism, then use case, then return shape. Every sentence contributes, though 'side-by-side' and 'surfaces which is most/least recognized' slightly restate the ranking claim in the same sentence.

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 tool with 4 parameters and no output schema, the description does supply a return shape ('ranked list with score, confidence, signal density per entity'), which is the main gap an agent would otherwise face. What remains unaddressed is the cost/latency profile of multi-model probing and any partial-failure behavior, which matters given the 2-8 entity bounds.

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 (entities, models, _apiKey, context) is already documented with formats and constraints, making the baseline 3. The description adds only the 'your brand + N competitors' framing, which largely repeats the schema's own note that the first entry is the subject.

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 ('Compare AI visibility across multiple entities side-by-side') and immediately explains the mechanism ('Probes each entity ... with ai_visibility_check, ranks by score'). It also distinguishes itself from the single-entity check by naming the underlying primitive, so an agent can tell the multi-entity comparison apart from a single lookup.

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 concrete context ('Useful for competitive AI-marketing audits') plus a quoted example question, which makes the intended scenario unambiguous. It implies but does not explicitly state the boundary against a single-entity ai_visibility_check call, and gives no exclusion criteria (e.g. when N=1 it is pointless), so it falls short of full when/when-not guidance.

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.