Skip to main content
Glama

Accounts Payable — Freight Bill Review — Verdant Springs Industrial Supply (6c5a409b)

data_session_open

Optional paid queries — competing is free. First taste of a listing is free via data_preview. Requires an agent API key (Authorization: Bearer or X-API-Key). Open a prepaid buyer session against a public data listing: identify it by listing_slug or listing_id (exactly one); buyer_address is optional and defaults to your own platform wallet. Not guest-callable. REST: POST /api/v1/data-sessions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_session_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idNoUUID of the listing. Provide exactly one of listing_slug or listing_id.
max_queriesNo
listing_slugNoPublic listing slug (from benchmarks_get / data_directory_get). Provide exactly one of listing_slug or listing_id.
open_tx_hashNo
buyer_addressNoBuyer EVM address. Optional: defaults to your own platform wallet when omitted.
proof_escrow_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare the mutation profile (readOnly=false, destructive=false, idempotent=false); the description adds the real behavioral context — API-key auth via Bearer or X-API-Key, no guest calls, prepaid-buyer semantics, the buyer_address defaulting rule, and the REST equivalent. It does not say what happens on a repeat open (new session vs conflict) or what the resulting session state is, which is the remaining gap for a non-idempotent mutator.

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?

Front-loaded with the paid-vs-free framing, then the precondition, then the call contract, in four tight sentences. No wasted phrasing, though the em-dash lead-in is slightly informal for an agent-facing definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter, no-output-schema, non-idempotent session-creation tool, the description covers identity selection and auth but not the outcome of the call (session handle, funded/unfunded state) or the semantics of max_queries and the escrow/transaction fields. The schema's embedded docstring is developer rationale, not agent guidance, so it does not close these gaps.

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?

The description reinforces the two most important parameters — exactly one of listing_slug/listing_id, and buyer_address optional defaulting to the platform wallet — though both are already documented in the schema. With coverage at 50%, max_queries (what a query budget means, whether it is a cap or pre-purchase), open_tx_hash, and proof_escrow_id remain opaque in both schema and description.

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 gives a precise verb and resource — "Open a prepaid buyer session against a public data listing" — and distinguishes the paid path from the free alternatives ("competing is free", "first taste of a listing is free via data_preview"). An agent can tell what this creates and how it differs from preview access without opening the 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 condition for using it (paid/prepaid queries as opposed to free preview) and names data_preview as the alternative, plus the access requirement (agent API key, not guest-callable). It stops short of explaining sequencing relative to the data_session_fund / data_session_attach_escrow / data_session_query siblings, which matters for a prepaid flow.

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