Skip to main content
Glama

AAAS Science Magazine research breakthrough news (scienceorgwatch)

data_session_release_with_delivery_proof

Idempotent

Requires an agent API key (Authorization: Bearer or X-API-Key). Release a funded data session's escrow to the pinned seller with the V2 dual-sig proof: the buyer DeliveryReceipt stored on the query row plus a DeliveryAttestation. Omit attestor_signature and the platform signs as reporter; relay=true lets it pay gas. The buyer or the seller's owner may call it. USDC moves escrow to seller, never to the platform. Returns the settlement summary. REST twin: POST /api/v1/data-sessions/{session_id}/release-with-delivery-proof. Next: data_session_get.

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": {
      "session_id": "<session_id>"
    },
    "name": "data_session_release_with_delivery_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
relayNotrue (default): the platform gas-relays the release. false: you submit it yourself.
session_idYesUUID of a data session you opened (from data_session_open).
step_indexNoQuery step to settle (1-based). Omit to settle the latest.
buyer_receiptNoOptional override; defaults to the receipt stored on the query row.
release_tx_hashNoOptional hash of a release tx you already broadcast yourself. Required when relay is false.
attestor_signatureNoOptional 0x DeliveryAttestation signature. Omit it and the platform signs as the marketplace reporter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations cover safety (readOnlyHint=false, destructiveHint=false, idempotentHint=true) but say nothing about auth, actors, or fund flow; the description supplies all three: an agent API key via Bearer or X-API-Key, caller authorization limits, and the guarantee that USDC moves escrow to the seller and never to the platform. It also discloses the platform-as-reporter fallback when attestor_signature is omitted and the fact that a settlement summary is returned.

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?

Dense but front-loaded: funding state, recipient, and proof mechanism come first, then the conditional behaviors, then the REST twin and next step. The auth sentence and REST endpoint line are slightly boilerplate, but each sentence carries operational information.

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

Completeness4/5

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

For a 6-parameter mutation with a full schema and well-covering annotations, this is nearly complete: auth model, caller eligibility, funds destination, gas-relay behavior, fallback signing, and return value are all stated. The one gap is disambiguation from the near-identically named release siblings.

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 is already documented in the schema, including the relay and attestor_signature semantics the description restates. The description adds little parameter meaning beyond that (it does not clarify step_index/buyer_receipt override behavior), so the baseline 3 applies.

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?

Names a specific verb and resource ('Release a funded data session's escrow to the pinned seller') and pins down the mechanism ('V2 dual-sig proof: the buyer DeliveryReceipt ... plus a DeliveryAttestation'). It stops short of explicitly contrasting itself with the sibling data_session_release_with_proof, so an agent must infer which proof variant to pick from the name alone.

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

Usage Guidelines4/5

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

Gives real preconditions and routing guidance: caller must be the buyer or the seller's owner, relay=true lets the platform pay gas while relay=false means you submit it yourself, and 'Next: data_session_get' names the follow-up step. It provides no explicit when-not/exclusion against the closely named sibling release tools, which keeps it out of 5 territory.

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