Skip to main content
Glama

NoGPU

nogpu_delete

DestructiveIdempotent

Delete an uploaded job's data now (otherwise deleted within 24h, or 24h after payment if you bought the model).

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_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
claim_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety semantics are covered. The description adds real context annotations cannot express: the retention policy (auto-delete within 24h, or 24h after payment if the model was purchased), which is precisely the fact an agent needs to decide whether deletion is necessary. It still omits whether the claim_token is a one-time authorization and whether deletion is recoverable.

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?

A single sentence with the destructive action front-loaded and the retention caveat parenthesized rather than buried. The parenthetical is slightly dense ('24h after payment ') but nothing is wasted.

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 simple two-parameter destructive tool with no output schema, the description covers the action and the timing alternative fairly well. What remains missing is material: the provenance/role of claim_token and the scope of what data is actually removed.

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

Parameters2/5

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

Schema coverage is 0%, so the description carries full burden for both required parameters and adds nothing. 'job_id' is self-evident, but 'claim_token' is opaque — no hint about what it authorizes, where it comes from, or how it relates to the job.

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?

States a specific verb (Delete) and resource (an uploaded job's data) with an immediate-effect qualifier ('now'). Siblings are buy/report/status, none of which overlap with deletion, so the action is unambiguous even though no alternative deletion tool is named.

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 parenthetical 'otherwise deleted within 24h, or 24h after payment' implicitly tells the agent when this call matters (forcing deletion early rather than waiting for automatic cleanup), but it never explicitly says 'use this when you need immediate removal' or warns when not to call it.

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.