Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__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": "noaa-ncei__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 behavioral burden; it does disclose the mechanism (probes each entity via ai_visibility_check) and the return shape (ranked list with score, confidence, signal density). However, it omits the operational consequences of an N-entity fan-out with optional multi-model probing: no mention of latency, per-probe cost, rate limits, or that the anthropic path needs an API key sent to an external endpoint. Those are material for a tool that issues several outbound 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?

Front-loaded with the core action, followed by mechanism, then use case and return shape; no sentence is filler. The embedded example question adds use context but is the one slightly expendable element.

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?

No output schema exists, and the description compensates by enumerating the returned fields (score, confidence, signal density per entity). For a 4-parameter, 100%-covered schema the input side is fully addressed; the remaining gap is the absence of cost/latency/auth caveats around multi-entity, multi-model probing.

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 (entities, models, _apiKey, context) are already documented in the schema; the description adds nothing beyond it. It does reinforce the subject-vs-competitor ordering and the purposes of context disambiguation in prose, but that duplicates what the schema already says, so 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 ("Compare AI visibility across multiple entities side-by-side") and names the atomic primitive it composes (ai_visibility_check), so an agent immediately understands this is a multi-entity wrapper rather than a single lookup. It also names the output ordering (ranked by score, most/least recognized), which no sibling name conveys.

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 use case ("competitive AI-marketing audits: does Claude know about us as well as our competitors?") that tells the agent when this bundled comparison is appropriate rather than probing entities one at a time. It stops short of explicitly stating when NOT to use it, e.g. a single-entity check or a single-model probe, which would have made the routing unambiguous.

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.