Skip to main content
Glama

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

data_session_mark_released

Requires an agent API key (Authorization: Bearer or X-API-Key). Record that a data session you bought was released: you released it on-chain yourself (pass release_tx_hash), or it is a soft session. With on-chain escrow enforced the escrow must already read RELEASED. Needs at least one served query. Moves no funds. Returns the updated session. REST twin: POST /api/v1/data-sessions/{session_id}/mark-released. 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_mark_released"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesUUID of a data session you opened (from data_session_open).
release_tx_hashNoOptional 0x tx hash of the on-chain release or refund to record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Adds meaningful behavior beyond the annotations: API-key auth, 'Moves no funds', the escrow state precondition, and 'Returns the updated session'. However, annotations set idempotentHint=false and the description never warns that a repeat call on an already-marked session will fail, nor does it state what error surfaces when preconditions are unmet.

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 and every clause carries information: auth, purpose, two paths, preconditions, side-effect, return, REST twin, and next step. The auth requirement leads ahead of the actual purpose, which slightly delays the key information, and the telegraphic fragment style is terse but readable.

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 two-parameter mutation with no output schema, the description covers the important gaps: it says the response is the updated session, states no funds move, and lists the state preconditions. The main residual gap is idempotency/repeat-call behavior given idempotentHint=false.

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 both parameters are already documented, giving a baseline of 3. The description does add conditional meaning — release_tx_hash applies only when you released on-chain yourself, and is omitted for soft sessions — which is a modest lift above 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?

Specific verb plus resource: 'Record that a data session you bought was released', with the two qualifying paths (on-chain release with release_tx_hash, or a soft session) spelled out. It does not explicitly contrast itself with close siblings such as data_session_mark_refunded or the release_with_proof variants, so the agent must infer that boundary from names 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: you must have released on-chain yourself or hold a soft session, the escrow must already read RELEASED when escrow is enforced, and at least one query must have been served. What is missing is negative routing — nothing says which tool to use if the escrow is not yet RELEASED or if you want a refund instead.

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