Skip to main content
Glama

RICOVANT AI Visibility Auditor

audit_ai_visibility

Expanded website audit for a one-time $0.50 Stripe Checkout payment. Returns payment URL for checkout; audit delivered on secure checkout completion.

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": {
      "url": "<url>"
    },
    "name": "audit_ai_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTP(S) website URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the most consequential non-obvious behavior: this is a paid ($0.50 Stripe Checkout) operation that returns a payment URL rather than audit results, with delivery occurring after secure checkout completion. It does not cover timing, what happens if checkout is abandoned, or authentication expectations, but the critical payment/async trait is surfaced.

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?

Two compact sentences, no filler, with the pricing and payment-gating constraint front-loaded ahead of the return behavior. Every clause carries information an agent needs.

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

Completeness3/5

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

For a single-parameter tool the input side is fully covered, and the payment flow is explained. However, with no output schema, the description should at least characterize the deliverable (what an "expanded" audit contains or how results are retrieved), which it does not.

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?

There is a single parameter with 100% schema description coverage ("Public HTTP(S) website URL"), so the schema already does the work. The description adds no constraints such as whether non-public or non-HTTP URLs are rejected, leaving this at baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it performs an "expanded website audit," which gives a verb and resource, but never says what the audit actually examines (AI visibility is only inferable from the tool name). "Expanded" hints at a broader scope than the sibling check_ai_crawlers and check_structured_data tools without naming or characterizing them.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to call this instead of the sibling checks, nor any stated prerequisite such as running the free checks first. The word "Expanded" weakly implies a follow-up to a basic audit, but that is left entirely to inference.

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