Skip to main content
Glama

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

data_session_mark_refunded

Requires an agent API key (Authorization: Bearer or X-API-Key). Record that a data session you bought was refunded. With on-chain escrow enforced the escrow must already read REFUNDED (for example after its deadline). Pass the refund tx as release_tx_hash. Moves no funds. Returns the updated session. REST twin: POST /api/v1/data-sessions/{session_id}/mark-refunded. 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_refunded"
  }
}

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

A4.6/5.0
Behavior5/5

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

Beyond the annotations it discloses the auth requirement, the required escrow state, that no funds move, and that the updated session is returned — real behavioral context the mutation annotations (readOnly=false, idempotent=false, destructive=false) 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.

Conciseness5/5

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

Six short, front-loaded sentences in a logical order: auth, action, precondition, parameter, side-effect, return, REST twin, next step. Nothing is padded or repeated.

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?

With no output schema, the description compensates by stating the return (updated session), and it covers auth, preconditions, and the call chain. Only idempotency behavior for repeat calls with the same tx hash is left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so baseline is 3; the description adds value by clarifying that release_tx_hash should carry the refund tx specifically, resolving the mismatch between the field name and this tool's purpose.

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?

'Record that a data session you bought was refunded' gives a specific verb and resource, and the word 'refunded' cleanly separates it from the sibling data_session_mark_released without the agent needing to open 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 Guidelines4/5

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

It states the precondition for use (on-chain escrow must already read REFUNDED, e.g. after deadline) and points to the next step (data_session_get), giving solid context. It never explicitly names data_session_mark_released as the alternative for the release path, so the when-not-to-use case is only implied.

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