Skip to main content
Glama

site_check

Trigger an on-demand site check for a project. Usually returns the finished run with per-target details within ~10s; if probes are still executing it returns { run: { id, status: "running" } } — site_check_status has the result a moment later. It answers "is it back yet" after a fix, and serves as a post-deploy check.

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

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), the description discloses the expected latency (~10s) and the two possible return shapes, including the exact running-status payload. That is material behavioral context an agent cannot infer from the annotations, and it confirms the non-destructive framing.

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?

Three sentences, front-loaded with the action, then timing/return-shape, then usage framing. Dense and largely waste-free; the quoted phrasing 'is it back yet' is informal but functions as compact usage guidance rather than filler.

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?

There is no output schema, so the description must carry return-value meaning — and it does, spelling out both the finished-run case and the running case with a concrete payload. With one fully documented parameter and annotations covering the safety profile, nothing an agent needs to call this correctly 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 coverage is 100% and the project_id field already documents UUID, subdomain, slug, and the 'default' fallback with the multi-project error behavior. The description only restates 'for a project' and adds no resolution or format detail beyond the schema, so baseline 3 applies.

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?

The description opens with a specific verb and resource: 'Trigger an on-demand site check for a project.' It immediately distinguishes itself from the similarly named sibling site_check_status by explaining that the sibling retrieves the result of a still-running probe, so an agent can tell the two apart without inspecting schemas.

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

Usage Guidelines5/5

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

It gives explicit situations for use: 'is it back yet' verification after a fix and a post-deploy check. It also names the alternative (site_check_status) and the precise condition that routes to it — when the returned run has status 'running' — which is exactly the when/when-not guidance an agent needs.

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