Skip to main content
Glama

system_check

Verifies GPU readiness by reading driver version and available VRAM before starting ComfyUI workflows, without allocating CUDA tensors.

Instructions

Verify system readiness: GPU, driver, VRAM.

Reads the driver, not torch. This process never allocates CUDA tensors, so torch.cuda would report 0 whether or not ComfyUI is holding every byte.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 real work: it discloses that the process allocates no CUDA tensors and that torch.cuda would read 0 regardless of ComfyUI's memory use — a genuine interpretation caveat. It does not explicitly state read-only/no-side-effects, but 'Verify' plus the no-allocation note makes that near-unambiguous.

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 with the core purpose in one line, then a two-sentence caveat. The second and third sentences overlap somewhat (both explain driver-not-torch), but the third adds the concrete failure mode, so little is wasted. The block-quoted formatting is slightly odd but not confusing.

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?

An output schema exists, so return values need no explanation, and there are no parameters to document. What remains thin is what 'readiness' concretely means — pass/fail thresholds, and whether ComfyUI must be running for the check to be meaningful.

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?

Zero parameters, so there is nothing for the description to disambiguate. Baseline 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?

Specific verb plus enumerated resource: 'Verify system readiness: GPU, driver, VRAM.' An agent knows exactly what is inspected. It gestures at differentiation from CUDA-based checks ('Reads the driver, not torch') without naming the closest sibling (get_vram_usage), so it falls short of a 5.

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?

The driver-vs-torch note implies this is the authoritative check when CUDA reporting may be misleading, but the description never states when to prefer it over get_vram_usage or get_comfyui_status. Usage is inferable rather than declared.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.