Skip to main content
Glama

How AI sees a website

check_site
Read-onlyIdempotent

Runs OnMap.me's free check on any public website: can AI crawlers reach it, does it say what the business is, where it is and how to reach it, and what is missing. Returns each check with pass or fail and a short written read. Limited to a few checks an hour.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe website address, for example "example-bakery.com".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the bar is lower, and the description still adds real behavioral context: the check is free, it is rate-limited to 'a few checks an hour', and results come back as per-check pass/fail with a short written read. The rate-limit disclosure is exactly the kind of trait annotations cannot carry. Minor gap: it does not say what happens on unreachable or non-HTML URLs.

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 tight sentences that front-load the action and scope, then fold return shape and the rate limit into the closing clause. No filler wording; 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.

Completeness4/5

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

For a single-parameter, no-output-schema tool with rich annotations, the description is nearly sufficient: it explains what is measured, what is returned, and the throttling. It stops slightly short on failure modes and on whether the rate limit is per caller or global.

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?

Only one parameter and schema description coverage is 100%, with an example already supplied by the schema, so the baseline of 3 applies. The description adds the constraint that the target must be a public website address, but nothing about accepted formats (scheme, path, redirects) beyond that.

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?

States a specific verb ('Runs ... check') and resource ('any public website') and even enumerates the criteria checked: AI crawler reachability, business description, location, contact info, and gaps. The website scoping implicitly separates it from check_handle, but the description never names or contrasts a sibling explicitly.

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 implied rather than stated: the agent can infer this applies to public websites when the question is 'can AI crawlers see this site and does it convey the business info'. There is no explicit when-not guidance (e.g. private/intranet URLs, or when to prefer check_handle), and no prerequisite stated beyond 'public'.

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.