Skip to main content
Glama

SendGrid (Unofficial)

AI Visibility Check

ai_visibility_check
Read-onlyIdempotent

Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass _apiKey to also probe Anthropic (BYO key, you pay Anthropic directly for those calls). Returns per-model {score, confidence, signals, raw_response} + a combined view. Useful for AI-marketing audits, pre-launch brand checks, competitive monitoring.

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": {
      "entity": "Tesla"
    },
    "name": "ai_visibility_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityYesThe thing to ask about. Brand/business name, product name, person, or topic. E.g. "Pipeworx", "OpenInvoice", "Acme Corp pricing".
modelsNoWhich models to probe. Supported: "workers-ai" (free default), "anthropic" (requires _apiKey). Omit for just workers-ai.
_apiKeyNoOptional Anthropic API key (sk-ant-...), only needed if "anthropic" is in models. Passed straight through to api.anthropic.com.
contextNoOptional: a phrase locating the entity (e.g. "Boston restaurant", "B2B SaaS"). Helps disambiguate common names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Optional Anthropic API key (sk-ant-...) — only needed if \"anthropic\" is in models. Passed straight through to api.anthropic.com."New value: +"Optional Anthropic API key (sk-ant-...), only needed if \"anthropic\" is in models. Passed straight through to api.anthropic.com."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, non-destructive semantics, and the description adds genuinely new context on top: the free default model, that Anthropic calls are billed by the caller directly, that the key is passed straight through to api.anthropic.com, and the per-model return shape. With no output schema present, the return-value description is especially valuable; it omits latency, rate limits, and result variability across runs, which keeps it below a 5.

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 core purpose and scope are front-loaded in the first sentence, and every subsequent sentence adds cost, return-shape, or use-case information. It is somewhat dense with stacked parentheticals ('BYO key, you pay Anthropic directly for those calls'), but no sentence is truly wasted.

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 full schema coverage, annotations, and no output schema, the description supplies the two things that matter most: what comes back ({score, confidence, signals, raw_response} plus a combined view) and the cost/credential model. Remaining gaps such as latency, model-count limits, and result variability are minor rather than blocking.

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 coverage is 100%, so all four parameters, including supported model values and the _apiKey requirement, are already documented in the schema. The description only reinforces the free default (naming Llama-3.3-70b) and the BYO-key billing model, adding marginal meaning beyond the schema and matching the baseline of 3.

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 gives a specific verb and resource ('Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model'), which is immediately actionable. It does not explicitly distinguish itself from the sibling 'scan_competitor_ai_presence', whose name suggests overlapping brand-visibility probing, so the boundary is left to inference.

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 names concrete usage contexts (AI-marketing audits, pre-launch brand checks, competitive monitoring), which is clear when-to-use guidance. It offers no when-not guidance and does not name an alternative for the competitive-monitoring case, so it stops short of full routing 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.