Skip to main content
Glama

Venoh AI Visibility

Check AI visibility

check_ai_visibility
Read-only

Free check: asks Perplexity 5 questions a buyer would ask about the company's category and city, and shows whether the company is named and who is named instead. Once per email, and each website once a week. Takes about a minute.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "website": "<website>",
      "email": "<email>"
    },
    "name": "check_ai_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesWork email of the person asking (one free check per email)
marketNoCity or country the buyers are in, for example Pune or India. Defaults to India.
companyNoCompany name, if the homepage title isn't it
websiteYesThe company's website, for example acme.in
categoryNoWhat the company sells in 2 to 4 words, for example dental clinic. Read from the homepage when left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses cost (free), quota behavior (per email, per website weekly), runtime (~1 minute), and the shape of the result (whether the company is named and who appears instead). It does not say what happens when the quota is exhausted or whether a failed lookup still consumes the check, which would complete the picture.

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 short sentences, front-loaded with the key qualifier 'Free check' and then mechanism, limits, and duration in descending order of importance. Nothing is redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of describing the return and does so qualitatively, while also covering cost, rate limits, and latency. For a single-purpose read-only check, an agent has everything needed to decide and call it correctly.

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 five parameters are already documented in the input schema. The description reinforces the role of category and market by tying them to the questions asked, but adds no format, fallback, or validation detail beyond what the schema states.

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 names a concrete mechanism (Perplexity, 5 buyer-style questions scoped to category and city) and states the result (whether the company is named and who is named instead), so the resource and outcome are unambiguous. It stops short of distinguishing itself from the sibling find_buyer_questions, which could plausibly be confused as a prerequisite for this check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It conveys when this is appropriate (a free, self-serve visibility check) and encodes hard limits: once per email and once per website per week. However, it offers no explicit when-not guidance or pointer to an alternative such as find_buyer_questions, leaving the agent to infer the boundary.

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.

Resources