Skip to main content
Glama

audit_depin_gpu_sla_escrow

Idempotent

[Private] Is the rented GPU really what you paid for? Checks TFLOPS, VRAM, bandwidth and temperature against the contract. Example: minTflopsFp16=250, minVramGb=80.

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": {
      "benchmarkReport": "<benchmarkReport>"
    },
    "name": "audit_depin_gpu_sla_escrow"
  }
}

Input Schema

NameRequiredDescriptionDefault
minVramGbNoMinimum required GPU VRAM in gigabytes.
minTflopsFp16NoMinimum required FP16 compute throughput in TFLOPS.
maxTempCelsiusNoMaximum safe GPU operating temperature in Celsius.
benchmarkReportYesHardware telemetry object with measuredTflopsFp16, availableVramGb, and gpuTempCelsius.
minMemoryBandwidthGbsNoMinimum memory bandwidth in GB/s.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / benchmarkReport / description
      Added value: +"Hardware telemetry object with measuredTflopsFp16, availableVramGb, and gpuTempCelsius."
    • addedInput schema / properties / maxTempCelsius / description
      Added value: +"Maximum safe GPU operating temperature in Celsius."
    • addedInput schema / properties / minMemoryBandwidthGbs / description
      Added value: +"Minimum memory bandwidth in GB/s."
    • addedInput schema / properties / minTflopsFp16 / description
      Added value: +"Minimum required FP16 compute throughput in TFLOPS."
    • addedInput schema / properties / minVramGb / description
      Added value: +"Minimum required GPU VRAM in gigabytes."
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, yet the description only says the tool 'Checks' values — language that reads as a pure read operation. It never explains what non-read side effect occurs (presumably recording an audit verdict that gates the escrow), nor what happens on a failed threshold. The comparison axes are disclosed, but the consequential behavior an agent needs before calling a non-read-only escrow tool is not.

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?

Three short sentences, front-loaded with the core question and the measured dimensions, followed by a concrete example. The '[Private]' bracket is dead weight and the rhetorical opener costs a few words, but nothing else is padded.

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 five parameters including a nested telemetry object and no output schema, the description should say what the agent gets back — a pass/fail verdict, per-metric results, or an escrow outcome — and it does not. Measurement coverage and thresholding are adequately covered, but the result shape and downstream escrow effect remain unspecified.

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?

Schema description coverage is 100%, so every parameter including the nested benchmarkReport fields (measuredTflopsFp16, availableVramGb, gpuTempCelsius) is already documented in the schema. The description adds only illustrative magnitudes (minTflopsFp16=250, minVramGb=80), which helps calibrate realistic threshold values but adds no units, defaults, or failure semantics beyond the schema.

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 names a concrete verb (checks) and a concrete resource (rented GPU telemetry: TFLOPS, VRAM, bandwidth, temperature) compared against a contract SLA. That distinguishes it from sibling audits like audit_ai_inference_escrow or audit_quant_backtest_escrow, though it never names those siblings explicitly. The '[Private]' prefix is unexplained and adds noise rather than scope.

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 rhetorical framing 'Is the rented GPU really what you paid for?' implies the usage context: a buyer who has rented GPU hardware and received a benchmark report. There is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling audit tools, so the agent must infer routing from the name alone.

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.