Skip to main content
Glama

ScienceNews Magazine Articles — buy per-query in-session (scinewsmag)

data_session_release_with_proof

Idempotent

Requires an agent API key (Authorization: Bearer or X-API-Key). Release a data session's escrow with a buyer-signed CompletionProof. Only for sessions whose attestor is the buyer; marketplace sessions use data_session_release_with_delivery_proof. Args: signature (from the release package's sign_typed_data), relay, release_tx_hash. USDC moves escrow to seller_address. Returns the settlement summary. REST twin: POST /api/v1/data-sessions/{session_id}/release-with-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>",
      "signature": "<signature>"
    },
    "name": "data_session_release_with_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
relayNotrue (default): the platform gas-relays the release. false: you submit it yourself.
signatureYesBuyer's 65-byte 0x CompletionProof signature (sign_typed_data from data_session_release_package).
session_idYesUUID of a data session you opened (from data_session_open).
release_tx_hashNoOptional hash of a release tx you already broadcast yourself. Required when relay is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations it discloses the auth mechanism, the funding effect ("USDC moves escrow to seller_address"), the eligibility precondition, the relay behavior boundary, and that a settlement summary is returned. The annotations only flag idempotent/non-destructive/open-world, so this description carries the real behavioral load and does so concretely.

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

Conciseness5/5

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

Lead sentence carries auth, action, and object; the eligibility/exclusion clause follows immediately; parameters, effects, return, and REST twin are packed into short clauses with no filler. Every sentence supplies information an agent needs before calling.

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

Completeness5/5

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

For a state-changing, money-moving 4-parameter tool with no output schema, the definition covers preconditions, side effects, return content, and the next call. Nothing needed for correct invocation appears to be missing.

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 coverage is 100%, so the schema already explains relay, signature, session_id, and release_tx_hash, including the relay-false requirement. The description's arg list largely restates that, adding only the provenance hint that the signature comes from the release package's sign_typed_data, which is also in the schema text. Baseline 3 is appropriate.

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

Purpose5/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 data session's escrow with a buyer-signed CompletionProof") and immediately distinguishes itself from the sibling marketplace path by naming data_session_release_with_delivery_proof. An agent can select between the two release tools without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-not condition ("Only for sessions whose attestor is the buyer") paired with the named alternative for the excluded case. It also specifies prerequisites (agent API key) and a follow-up step ("Next: data_session_get"), so the surrounding workflow is covered.

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