Skip to main content
Glama

site_check_status

Read-onlyIdempotent

Get the latest smoke-test run for a project plus a short history. Smoke runs are auto-wired — homepage and any attached custom domains are probed every ~20 min and after every deploy. Status is "pass" / "fail" / "partial". Each run includes per-target details (URL, HTTP code, duration).

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_status"
  }
}

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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description doesn't need to argue safety. It instead adds genuinely new context: probes run every ~20 minutes and after each deploy, meaning results may lag reality, and the status vocabulary is pass/fail/partial. The per-target detail list (URL, HTTP code, duration) further discloses the return shape without an output schema.

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?

Four short sentences, front-loaded with what is returned, followed by operational context and status vocabulary. Every sentence carries information; the only slight looseness is the vague 'short history', which is never quantified.

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?

With no output schema, the description does a fair job describing return contents (status vocabulary, per-target fields). But 'a short history' is left undefined — no indication of how many runs, ordering, or whether history depth is configurable — which is a real gap for an agent interpreting results.

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?

The single parameter is fully documented in the schema (100% coverage), including the UUID/subdomain/slug resolution and the 'default' fallback behavior. The description adds nothing about project_id, so the baseline 3 for high schema coverage 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 opens with a specific verb and resource: 'Get the latest smoke-test run for a project plus a short history.' That is far more than a restatement of the name and tells an agent exactly what data comes back. It does not explicitly contrast itself with the sibling 'site_check', so the distinction between reading status and triggering a check is left to inference.

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?

There is no explicit when-to-use statement or named alternative. However, 'Smoke runs are auto-wired — ... probed every ~20 min and after every deploy' implies this tool is a read-only reporter and that no manual trigger is needed, which is a usable but indirect usage cue.

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