Skip to main content
Glama

Default-watch and pinning service

delta_run

Golden-task delta run, x402 pay-per-call $0.01/run: send the X-PAYMENT header on the /mcp request; without a verified payment the call answers HTTP 402 with the x402 challenge. Arguments are exactly the POST /delta-run body (see /docs).

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": {
      "platform_id": "<platform_id>",
      "old_model": "<old_model>",
      "new_model": "<new_model>"
    },
    "name": "delta_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasksNo
new_modelYes
old_modelYes
new_profileNo
old_profileNo
platform_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/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 disclose genuinely non-obvious behavior: a $0.01 per-call x402 charge and an HTTP 402 challenge when payment is unverified. However it says nothing about runtime, side effects, idempotency, limits on tasks, or what a successful call produces, which leaves the mutation/execution profile opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the cost and payment mechanics, which is the most actionable part. But the closing pointer to /docs and the POST body statement consume space without giving the agent any usable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, no annotations, six parameters with zero schema coverage and nested objects — the description should explain the delta-run concept and the shape of old/new model/profile/tasks, but it does not. Payment mechanics are covered; everything else an agent needs to invoke this correctly is missing.

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% and there are six parameters including nested objects (tasks, old_profile/new_profile). The description adds zero meaning — it merely says the arguments are the POST /delta-run body and points to external /docs, which is a deferral rather than an explanation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Golden-task delta run" names the resource but never states the verb or the outcome — an agent cannot tell from the text that this runs a set of golden tasks against an old vs new model and diffs the results. It is at least distinguishable from all siblings (ingest_changelog, probe, etc.), so it avoids a 2.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says nothing about when to call this versus probe, verify_attestation, or any sibling, and gives no prerequisites beyond payment. The only usage instruction is about the X-PAYMENT header, not about task selection.

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.

Resources