Skip to main content
Glama

AAAS Science Magazine research breakthrough news (scienceorgwatch)

data_session_signing_payload

Read-onlyIdempotent

Requires an agent API key (Authorization: Bearer or X-API-Key). Get the exact EIP-712 DeliveryReceipt typed data to sign for one query on a funded session (queryHash = sha256(query), stepIndex = queries_used + 1). Args: session_id, query (the exact text you will send). Sign it with the buyer_address key and pass the 65-byte signature as delivery_receipt. REST twin: GET /api/v1/data-sessions/{session_id}/signing-payload?query=. Next: data_session_query with delivery_receipt.

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>",
      "query": "<query>"
    },
    "name": "data_session_signing_payload"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesExact query text you will send to data_session_query. queryHash is sha256 of this text, so sign for the same string you query with.
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/5.0
Behavior5/5

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

Annotations only declare it as a safe, idempotent read; the description adds what actually matters operationally: the auth header forms, the deterministic derivation queryHash = sha256(query) and stepIndex = queries_used + 1, and the requirement to sign with the buyer_address key and pass a 65-byte signature as delivery_receipt. That derivation detail is correctness-critical and appears nowhere in the annotations or schema.

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?

It is dense but well front-loaded: auth, then the core action, then derivation rules, then the handoff. The 'Args:' clause largely restates the schema and could be trimmed, but the rest of every sentence carries real information.

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 adequately characterizes the return value as EIP-712 typed data and explains how to use it. It does not cover the payload's lifetime or what happens if the signed query differs at query time, which are the remaining gaps for a signing flow.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that session_id must reference a funded session and that the query text is hashed into queryHash, so the same string must be reused at query time.

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?

The description names a specific verb and resource: retrieve the exact EIP-712 DeliveryReceipt typed data to sign for one query on a funded session. It is instantly distinguishable from siblings like data_session_query or data_session_fund, and it names the downstream call that consumes the output.

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 establishes the prerequisites (agent API key, a funded session) and explicitly routes forward: 'Next: data_session_query with delivery_receipt.' What is missing is an explicit fallback branch, e.g. what to call first if the session is not yet funded, so an agent must infer data_session_fund.

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