Skip to main content
Glama

NoGPU

nogpu_buy

Read-only

Read-only, never pays: for a certified (fit) report, returns the $99 offer to keep the model, the question to ask the user word for word, a card checkout link for the user, and the USDC (x402) payment details when the server offers them. If the job is not buyable, returns the reason.

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

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 readOnlyHint=true, and the description reinforces this with 'never pays', which tells the agent no charge is incurred. It also discloses conditional behavior (x402 details only when the server offers them) and a failure path (returns the reason when not buyable). Missing are any notes on auth requirements for claim_token or how the returned question should be relayed.

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 dense sentence, but the most decision-relevant facts ('Read-only, never pays') are front-loaded and the enumerated returns are easy to scan. There is little filler, though the run-on length slightly hurts readability.

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?

With no output schema, the description does the necessary work of enumerating what is returned, which is the right call. It remains incomplete on the input side (job_id, claim_token) and on prerequisites such as where a claim_token comes from or what happens if it is stale.

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 description coverage is 0% for job_id and claim_token, and the description never mentions either parameter or its format/provenance. With both parameters required and completely undocumented, the description fails to compensate for the schema gap.

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 makes the resource and effect concrete: it returns a $99 keep-the-model offer, the exact user question, a card checkout link, and USDC/x402 payment details for a certified (fit) report. The explicit 'never pays' also pre-empts a wrong reading of the name 'buy'. It does not differentiate itself from siblings like nogpu_report or nogpu_status, 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?

A prerequisite is implied ('for a certified (fit) report') and a negative branch is covered ('if the job is not buyable, returns the reason'). However, there is no explicit statement of when an agent should call this instead of nogpu_report or nogpu_status, so the routing decision is left to inference.

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.