Skip to main content
Glama

NoGPU

nogpu_status

Read-only

A job's status, and its report once ready (same fields as nogpu_report). Also shows download_url after payment: GET it with header X-Claim-Token. claim_token and report_url are secrets.

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": {
      "job_id": "<job_id>",
      "claim_token": "<claim_token>"
    },
    "name": "nogpu_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
claim_tokenYes

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 only cover readOnlyHint and openWorldHint, so the description carries the rest and does add real value: the staged return (status first, report later), the post-payment appearance of download_url, and the required X-Claim-Token header. The warning that claim_token and report_url are secrets is security context an agent cannot get from structured fields.

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?

Compact and reasonably front-loaded, leading with what is returned before the payment/download mechanics. The compressed phrasing around 'GET it with header X-Claim-Token' and the embedded whitespace make it slightly harder to parse than necessary.

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?

For a two-required-parameter read tool with no output schema, it covers the return payload and the secure-download flow. It omits what happens when the job is unfinished, expected polling cadence, and any error behavior, which an agent invoking this repeatedly would want.

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?

With 0% schema description coverage, the description must compensate and only partly does: claim_token is characterized as a secret and tied to the X-Claim-Token header, but job_id is never explained beyond 'a job's'. The header/parameter relationship is also ambiguous since claim_token appears in both the schema and a GET header.

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 states the specific resource (a job's status) and its progressive return (the report once ready), and explicitly ties the report fields to those of nogpu_report. The verb is implicit ("A job's status, and its report") rather than an explicit 'retrieves/returns', which keeps it just 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?

It implies the polling use case (status now, report once ready) and notes download_url appears only after payment, which is real usage context. It never says when to prefer this over nogpu_report or what to do while the job is not ready, so guidance is implied rather than stated.

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.