Skip to main content
Glama

AAAS Science Magazine research breakthrough news (scienceorgwatch)

data_session_release_package

Read-onlyIdempotent

Requires an agent API key (Authorization: Bearer or X-API-Key). Get everything needed to settle a data session: attestations, chain validity, the task spec, the top-level sign_typed_data hop, the CompletionProof and, on V2 receipted sessions, the dual-sig delivery_proof. Use after your queries. Read-only; nothing moves. REST twin: GET /api/v1/data-sessions/{session_id}/release-package. Next: data_session_release_with_delivery_proof (marketplace sessions) or data_session_release_with_proof (attestor is the buyer).

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

Input Schema

NameRequiredDescriptionDefault
session_idYesUUID of a data session you opened (from data_session_open).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so 'Read-only; nothing moves' is mostly redundant. The description still earns credit for disclosing the auth requirement (Bearer or X-API-Key, owner derived from the key) and a conditional output shape — the dual-sig delivery_proof appears only on V2 receipted sessions — which annotations do not convey.

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 readable, with the payload list and the next-step routing each occupying one clause. The auth line is front-loaded ahead of the purpose, which is slightly suboptimal ordering, and 'Read-only; nothing moves' restates the annotation, but neither costs much.

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?

With no output schema, the description carries the return-value burden and does so by naming every element of the release package, including the conditional delivery_proof. Auth, REST twin, and successor tools are all present, leaving nothing an agent needs before calling it.

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?

There is a single parameter at 100% schema coverage, and the schema already explains it is the UUID from data_session_open with the owner bound to the key. The description adds no syntax or scoping detail about session_id, so the baseline 3 applies.

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?

States a concrete verb+resource ('Get everything needed to settle a data session') and then enumerates the payload (attestations, chain validity, task spec, sign_typed_data hop, CompletionProof, delivery_proof). It also distinguishes itself from the sibling release tools by naming them as downstream steps, so an agent can place it without opening any 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?

'Use after your queries' fixes the position in the workflow, and 'Next: data_session_release_with_delivery_proof (marketplace sessions) or data_session_release_with_proof (attestor is the buyer)' gives explicit alternatives with the condition that selects each. That is when-to-use plus routing, not 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.

Resources