Skip to main content
Glama
Sign In

AISeeWhy

by com.aiseewhy
OverviewDiscussionsAdmin

audit_url

Read-onlyIdempotent

Audit one URL: fetch it as 16 AI and search crawlers plus curl and a browser, check robots.txt, structured data, answer-first content, freshness, hreflang and llms.txt, plus classic on-page SEO (title, meta description, H1, canonical, noindex, image alt text, broken links). Returns a Markdown report with findings and fixes. language: report language code (en, de, ja, …).

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_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage to audit: a full URL or a bare domain such as example.com (https is assumed).
botsNoOnly test these crawlers, by name (for example GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended). Omit to test all 16 AI and search crawlers.
languageNoReport language as a code such as en, de, fr, es, ja or zh. Defaults to the account language (English without a key); 30 languages are supported.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / bots / description
      Added value: +"Only test these crawlers, by name (for example GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended). Omit to test all 16 AI and search crawlers."
    • addedInput schema / properties / language / description
      Added value: +"Report language as a code such as en, de, fr, es, ja or zh. Defaults to the account language (English without a key); 30 languages are supported."
    • addedInput schema / properties / url / description
      Added value: +"Page to audit: a full URL or a bare domain such as example.com (https is assumed)."
  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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context: it fetches as 16 crawler user agents plus curl and a browser, and it returns a Markdown report with findings and fixes, which tells the agent what to expect from an open-world fetch.

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 capability is front-loaded in a dense but well-ordered first sentence, and the enumerated checks earn their space. The trailing language fragment is slightly orphaned and restates the schema, which keeps it from being maximally tight.

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 read-only, idempotent single-URL audit with an output schema present, the description covers what is checked, how many crawlers are exercised, and the report format. The bots parameter's filtering behavior is left entirely to the schema, but that is acceptable given full schema coverage.

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 url, bots and language are already fully documented in the schema. The description only restates the language parameter ('report language code (en, de, ja, …)') and adds no syntax or behavioral detail beyond it. Baseline 3 applies since the schema does the heavy lifting.

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?

The description names a specific verb (audit) and resource (one URL) and enumerates the concrete checks performed (16 AI/search crawlers, curl, browser, robots.txt, structured data, llms.txt, classic on-page SEO). An agent can distinguish this from crawl_site or audit_sitemap purely from the description.

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?

Usage is only implied by the scope word 'one URL' and the single-URL framing; there is no explicit statement of when to prefer this over compare_urls, crawl_site or audit_sitemap. The agent must infer that this is the single-page check versus site-wide or comparative tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AISeeWhy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources