Skip to main content
Glama

list_warm_runs

List the inline warm runs of a site (most recent first) to poll their status after warm_site. Each run carries validation_status (verified, to_fix, probable, not_verified, in_progress) and the validation block when a post-warm check was requested. probable means the site sends no cache status header, so the check could only compare response times. Requires the boosts:read scope.

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": {
      "site_id": "<site_id>"
    },
    "name": "list_warm_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (max 100).
offsetNoNumber of runs to skip.
site_idYesID of the site whose warm runs to list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it declares ordering, enumerates validation_status values with an explanation of the ambiguous one ('probable means the site sends no cache status header, so the check could only compare response times'), notes the conditional validation block, and states the required boosts:read scope. It does not cover pagination behavior or what an empty result means, which keeps it out of the top band.

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?

The purpose and ordering are front-loaded in the first clause, and the remaining sentences explain return semantics and auth rather than padding. The enumerated status list is dense but each value earns its place by disambiguating the response.

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?

There is no output schema, so the description correctly compensates by explaining the returned validation_status values and the conditional validation block. Combined with the scope requirement, an agent has enough to call and interpret it; only pagination defaults and empty-result semantics are absent.

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 description coverage is 100%, so limit, offset, and site_id are already fully documented as page size, skip count, and target site. The description adds no syntax, defaults, or edge-case behavior for these parameters, which is the expected baseline when the schema does the work.

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 ('List the inline warm runs of a site') and adds ordering ('most recent first') plus the operational purpose ('to poll their status after warm_site'). The qualifier 'inline warm runs' distinguishes it from the sibling list_runs, so an agent can pick correctly without opening either schema.

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?

It states a clear use condition: poll run status after calling warm_site. That gives the agent a definite entry point. It stops short of an explicit exclusion (e.g. 'use list_runs for non-warm runs'), so it falls short of the top tier.

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