Skip to main content
Glama

get_config_check

Get a cache configuration diagnostic: pass check_id for one check, or site_id for the site's most recent check whatever its status. Returns status (pending, running, done, error; error_code tells why a check failed), score 0-100 (capped at 49 while a critical criterion fails), coverage (share of criteria that could be evaluated), sources (http, cloudflare, wordpress), the detected stack (CDN, cache plugin, host), counts per status, action_plan (up to 3 criteria to fix first, with the score gain of each) and results: one entry per criterion with criterion_id (e.g. html.edge_hit), status (pass, warn, fail, skip = data unavailable, na = not applicable, info), weight (10 critical, 5 major, 2 minor, 0 info) and evidence {code, params}. Requires the sites:read scope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_config_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoID of a site: fetch its most recent config check. Omit when passing check_id.
check_idNoID of the config check to fetch (as returned by check_cache_config). Omit when passing site_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 well: it declares the sites:read scope requirement, defines every status value and what error_code means, explains the score cap of 49 while a critical criterion fails, and defines coverage, weight tiers, and skip/na semantics. It omits failure behavior (e.g., site with no checks) and any rate-limit or caching notes.

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 correctly: selection logic first, then return payload. It is a single dense run-on sentence enumerating return fields, which is heavy but nearly all clauses carry actionable information given there is no output schema.

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?

Because no output schema exists, the description must describe returns, and it does so thoroughly (status, score, coverage, sources, stack, counts, action_plan, per-criterion results). The main gap is that both parameters are optional with no stated behavior when neither is provided, leaving the call contract ambiguous.

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 both property descriptions already state 'Omit when passing the other', so the description largely restates the schema's mutual-exclusivity rule. No additional format or precedence guidance (e.g., what happens if both are given) is added, 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?

States a specific verb+resource ("Get a cache configuration diagnostic") and immediately specifies the two lookup modes (check_id for one check, site_id for the most recent). An agent can tell this is a retrieval of an existing check result, distinct from the check-running sibling implied by check_cache_config in the 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?

Explicitly says which identifier to pass for which outcome, including the nuance that site_id returns the most recent check "whatever its status." It does not state what to do if neither is supplied, nor explicitly steer the agent to check_cache_config when no check exists yet.

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