Skip to main content
Glama

Run a free site check

check_site

Free. Reads a website's public facts: HTTPS and headers, certificate dates, SPF and DMARC, privacy, terms and contact pages, llms.txt, robots.txt and MCP labels. At most 24 requests, one over plain http, and up to 5 of them to its MCP server (mcp_url, or one the site names). Never logs in or posts forms. Each check: pass, warn, fail or not checked, with fixes. It saves the result: the same domain within 15 minutes gives it again (cached true) unless fresh is true. A public badge for your owner's domain, checked daily: prove_domain, then buy_site_badge on your human's yes. Not a security audit.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "example.com",
      "mcp_url": "https://example.com/mcp"
    },
    "name": "check_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNotrue: check again now.
domainYesLike example.com, no https:// or path.
mcp_urlNoIts MCP server if any: https on the same domain, like https://example.com/mcp.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "domain": "example.com",
      +    "mcp_url": "https://example.com/mcp"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare openWorld true and readOnlyHint false, and the description adds substantial context: a request budget (max 24, one over plain http, up to 5 to the MCP server), 'never logs in or posts forms', and the 15-minute cache with a fresh override. That is genuinely valuable disclosure beyond the annotations, though the return payload is only loosely sketched (pass/warn/fail/not checked with fixes).

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?

Front-loaded with cost and scope, then constraints, then caching, then the badge upsell. Dense and telegraphic but every clause carries operational information; the badge sentence is the least essential part of a site-check definition.

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 four-parameter, no-output-schema tool this covers the important ground: what is fetched, request limits, no auth/post behavior, cache semantics, and result categories. An agent could call it correctly without further reading.

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 coverage is 100%, so domain, mcp_url, fresh and passport_token are already documented in the schema. The description only adds that the MCP budget is spent on mcp_url 'or one the site names', a marginal gain over the schema.

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?

Specific verb and resource with an enumerated scope: HTTPS and headers, certificate dates, SPF/DMARC, privacy/terms/contact pages, llms.txt, robots.txt and MCP labels. The closing 'Not a security audit' and the named badge flow (prove_domain, buy_site_badge) make clear what this tool is and is not relative to siblings.

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

Usage Guidelines4/5

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

Gives clear context for use (reading a site's public facts) and an explicit exclusion ('Not a security audit'), plus the adjacent badge flow. It stops short of naming alternatives for overlapping needs such as email checks, so no explicit when-to-use-instead routing.

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.