Skip to main content
Glama

AI Site Scorer

analyze_url

Submit a URL for AI-readiness analysis. Checks how well the site is structured for AI/LLM crawling (robots.txt, structured data, page speed, content quality, etc.). Returns scores and recommendations. Set wait_for_result=true to wait for completion (up to 60s). Pricing: Free for registered users within fair-use limits; Pro subscription for high volume. Without an account (optional x402):$0.001 USDC for analysis only; $0.006 USDC combined when enhance=true ($0.001 analyze + $0.005 enhance, charged as a single upfront payment so only one X-PAYMENT header is needed per request).

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": "analyze_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to analyze (must include http:// or https://).
enhanceNoIf true, automatically run LLM deep analysis after basic analysis completes. Anonymous users: combined $0.006 USDC ($0.001 analyze + $0.005 enhance) charged as a single upfront payment. Default: false.
wait_for_resultNoIf true (default), wait for the analysis to complete and return the full report. If false, return the job_id immediately.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / enhance / description
      Previous value: -"If true, automatically run LLM deep analysis after basic analysis completes. Anonymous users: combined $0.06 USDC ($0.01 analyze + $0.05 enhance) charged as a single upfront payment. Default: false."New value: +"If true, automatically run LLM deep analysis after basic analysis completes. Anonymous users: combined $0.006 USDC ($0.001 analyze + $0.005 enhance) charged as a single upfront payment. Default: false."
  2. First observed

TDQS

A3.6/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 mostly succeeds: it discloses that the call can be synchronous or asynchronous (job_id), the 60s wait ceiling, that enhance triggers a follow-on LLM pass, and detailed payment mechanics including the single upfront X-PAYMENT charge for anonymous users. Remaining gaps are failure/timeout behavior after 60s and what happens to unclaimed job_ids.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core capability and the wait_for_result behavior are front-loaded and efficient. The trailing pricing sentence is long, restates the enhance price breakdown that already appears in the enhance parameter description, and buries the practically important x402/X-PAYMENT detail in a dense clause.

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 three-parameter submission tool with no annotations and no output schema, the description covers the main things an agent needs: what is analyzed, that results are scores plus recommendations, the sync/async switch, and the cost model. It could say more about report retrieval via get_report after an async submission, but nothing essential is missing.

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 the schema already defines url, enhance, and wait_for_result, including the combined pricing for enhance. The description adds only the 60s timeout ceiling, which is not in the schema. Baseline 3 is appropriate given the schema does the heavy lifting.

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 concrete verb and resource ('Submit a URL for AI-readiness analysis') and enumerates what is checked (robots.txt, structured data, page speed, content quality) plus the output shape (scores and recommendations). It does not explicitly distinguish this from siblings like scan_site or enhance_report, so an agent must infer the boundary, but the purpose itself is unambiguous.

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 context is implied through the wait_for_result guidance ('wait for completion up to 60s' vs returning a job_id) and the pricing tiers, which indirectly say when this is cost-effective. However, there is no explicit when-to-use/when-not-to-use statement and no named alternative such as scan_site or enhance_report for cases where a deeper or bulk operation is wanted.

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