Skip to main content
Glama

AAAS Science Magazine research breakthrough news (scienceorgwatch)

data_session_get

Read-onlyIdempotent

Requires an agent API key (Authorization: Bearer or X-API-Key). Read one data session you opened: status, escrow id, committed root, price, queries used and remaining, seller and attestor addresses. Use it to check where a purchase stands (open, funded, released, refunded). Returns the same session object data_session_open returns. REST twin: GET /api/v1/data-sessions/{session_id}. Next: data_session_query while queries remain, then data_session_release_package.

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

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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds real context beyond them: an auth requirement (agent API key via Authorization: Bearer or X-API-Key), ownership scoping (only sessions you opened; owner derives from the key), and that the returned object matches data_session_open's. Nothing about rate limits or error behavior, so it is solid but not rich.

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?

Three dense sentences, front-loaded with the auth prerequisite and then purpose, return fields, and next steps. Slight redundancy between listing the returned fields and the closing 'Returns the same session object data_session_open returns,' but nothing is wasteful enough to obscure the call path.

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?

There is no output schema, so enumerating the returned fields is exactly the compensating detail needed, and the description also supplies auth, ownership scoping, and REST twin. For a single-parameter read tool, an agent has everything required to invoke it and interpret the result.

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% and the single session_id param already documents itself as the UUID from data_session_open. The description's 'one data session you opened' and the owner-from-key note reinforce scope but add no new syntax or format detail beyond the schema. 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 precise verb (read) and resource (one data session you opened), then enumerates the returned fields: status, escrow id, committed root, price, queries used/remaining, seller and attestor addresses. It also names its REST twin (GET /api/v1/data-sessions/{session_id}), so an agent can distinguish it from the many sibling data_session_* mutation tools without opening a 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?

Explicit use case: check where a purchase stands (open, funded, released, refunded), and it chains forward with 'Next: data_session_query while queries remain, then data_session_release_package.' It does not explicitly say when NOT to use it or distinguish it from data_session_queries, but the lifecycle sequencing gives clear routing.

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