Skip to main content
Glama

SCRIPTMASTERLABS — Provider Trust + CANON

Check Status

check_status
Read-onlyIdempotent

Check whether the Provider Trust backend is live: returns the authoritative backend status envelope for the service that powers verify_provider, compare_providers, and the other checks. Use it to distinguish a Provider Trust outage from a target-side evidence gap before relying on any check result. Free, read-only.

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": "check_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so 'Free, read-only' mostly restates what is structured. The genuinely additive behavioral detail is that the response is the authoritative status envelope for the backing service, but permissions, failure modes, and latency/caching behavior are not described. With annotations carrying the safety profile, this is adequate rather than rich.

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?

Two sentences: the first states what is returned, the second states when to use it. The purpose is front-loaded and no sentence is padding, though 'Free, read-only' is close to redundant with the annotations.

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?

For a no-argument health-check tool this is largely complete: it says what the call returns, what it is for, and that it is safe and free. The one gap is that, with no output schema, the description never sketches what the 'status envelope' contains (e.g., status field values), so an agent cannot anticipate how to interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to explain and the baseline of 4 applies. The description correctly adds no unnecessary argument discussion.

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 states a specific verb and resource ('Check whether the Provider Trust backend is live') and immediately names the return artifact ('the authoritative backend status envelope'). It also ties the tool to the sibling checks it underpins (verify_provider, compare_providers), so an agent can distinguish it from those tools without opening a 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 gives a concrete trigger: call this to distinguish a Provider Trust outage from a target-side evidence gap before trusting any check result. That is clear usage context, but there is no explicit statement of when-not to call it or which alternative to prefer in ambiguous cases.

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