Skip to main content
Glama

Sitesy Website Intelligence

Quick site check

site_check
Read-onlyIdempotent

Quick check of one site: HTTPS reachability, plain HTTP behaviour, certificate days remaining, and which security headers are present. Costs 0.001 USDC per call. The caller pays per call in USDC on Base through x402: the first call returns the payment requirements, and an x402 aware MCP client signs and retries automatically.

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": {
      "domain": "<domain>"
    },
    "name": "site_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesA domain name, for example example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations, the description adds important behavior: the tool costs 0.001 USDC per call, uses x402 payment on Base, returns payment requirements on the first call, and expects an x402-aware MCP client to sign and retry automatically. This is critical operational context that an agent could not infer from the read-only and idempotent annotations.

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?

The description is front-loaded with the tool purpose, then gives the essential payment and retry behavior. It uses three sentences with no unnecessary wording, and the payment detail is necessary because it affects how the caller must handle the first response.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

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

For a single-parameter, read-only, idempotent check with no output schema, the description provides enough context: what is checked, the domain input expectation via schema, and the full payment flow. The listed checks communicate the result substance even though the exact response shape is not specified.

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 only one parameter, domain, and the schema description coverage is 100%, including type, length limits, and an example. The description does not add further domain syntax or validation details beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 resource and scope: a quick check of one site covering HTTPS reachability, HTTP behavior, certificate days remaining, and security headers. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as dns_posture, redirect_trace, or domain_profile.

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 phrase 'Quick check' implies a lightweight use case, but the description gives no explicit when-to-use guidance and does not mention alternatives or when not to use this tool. It also does not route the caller to siblings for deeper checks or different scopes.

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