Skip to main content
Glama

AI Site Scorer

scan_site

Scan a URL with methodology v2: three independent indices (access for AI search, content citability, agent readiness), stop factors and the top fixes ranked by evidence level. Same access/pricing as analyze_url.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL to scan

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description bears the full disclosure burden; it helpfully states the output components (indices, stop factors, evidence-ranked fixes) and that pricing matches analyze_url. It omits whether the scan is read-only, any latency/rate characteristics, or side effects — meaningful gaps for a no-annotation tool.

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?

Two dense sentences with no filler, and the methodology/output summary is front-loaded before the pricing note. Nothing extraneous, though the output list is slightly packed.

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 one-parameter scan with no output schema, describing the returned indices and fixes is valuable and mostly sufficient. However, the relationship to analyze_url is left ambiguous, which matters for an agent choosing between adjacent tools.

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, so the schema already documents 'url' as the page to scan. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 specific verb+resource ('Scan a URL') and enumerates what the scan produces (three independent indices for AI search access, content citability, agent readiness, plus stop factors and ranked top fixes), which is far more than restating the name. It stops short of clearly distinguishing the tool's purpose from the sibling analyze_url beyond noting shared access/pricing.

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?

The only usage-adjacent hint is 'Same access/pricing as analyze_url,' which speaks to cost rather than when to choose this tool over that sibling. There is no explicit when-to-use, when-not-to-use, or alternative-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.

Resources