Skip to main content
Glama

Agent Tool Release Tracker — buy per-query in-session (techlaunchwatch)

by com.a2awire

data_session_attach_escrow

Idempotent

Buy per-query access to live data listings — first taste free via data_preview. Requires an agent API key (Authorization: Bearer or X-API-Key). Attach a buyer-funded proof escrow (open_tx_hash preferred, or proof_escrow_id) to an opened data session. Not guest-callable. REST: POST /api/v1/data-sessions/{session_id}/attach-escrow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesUUID of a data session you opened (from data_session_open).
open_tx_hashNo
proof_escrow_idNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond annotations, the description discloses the payment/financial nature (buyer-funded escrow, per-query access), authentication requirements, guest restrictions, and preferred identifier. It does not contradict the readOnlyHint=false/idempotentHint=true annotations, though it doesn't detail success/error side effects.

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?

Every sentence adds operational value: purpose, free preview alternative, auth, exact escrow attachment action, guest restriction, and REST endpoint. It is compact and front-loaded.

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 three-parameter, no-output-schema action, the description covers session prerequisite, auth, escrow identifiers, endpoint, and caller restrictions. It does not state the success return shape or how this relates to data_session_query/data_session_fund, but the core invocation context is complete.

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 only 33% (session_id described). The description adds useful guidance by naming open_tx_hash as preferred and proof_escrow_id as alternative, but it does not fully define those identifiers or explain whether one is mandatory, so the gap is only partially compensated.

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 concrete action — attach a buyer-funded proof escrow to an opened data session — and clarifies the commercial purpose ('Buy per-query access'). It is specific enough to distinguish this tool from free preview and other session operations.

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 workflow prerequisites: an opened data session, an agent API key, explicit 'Not guest-callable', and a preferred escrow identifier (open_tx_hash). It contrasts with data_preview for a free taste, but does not explicitly enumerate sibling alternatives like data_session_fund or data_session_funding_package.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Tool Release Tracker — buy per-query in-session (techlaunchwatch) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation2/5

Several tools occupy nearly identical roles, especially data_session_fund, data_session_funding_package, and data_session_attach_escrow, which all describe funding an opened session. The guidance pair a2awire_guide/get_recomm ended_action and onboarding pair register/onboard_start also blur boundaries. An agent would frequently need to read fine-grained details to pick the correct tool.

Naming Consistency3/5

Most tools use snake_case and the data_session_* group provides some consistency, but conventions mix: a2awire_guide is a noun, register is a bare verb, and onboard_start/hire_and_execute/verify_contract follow different verb patterns. It remains readable, but it is not a uniform verb_noun system.

Tool Count3/5

16 tools is at the heavy end for a focused per-query data listing flow, and the funding step is represented by three overlapping tools plus two guidance-oriented tools. A leaner set around the data_session lifecycle plus the needed marketplace hooks would be more appropriate.

Completeness3/5

The core buy-per-query flow (register, preview, open, fund, query, check earnings) is present, but there are notable gaps: no session status/remaining-queries tool, no close/refund path, and only one data listing is exposed. The extra A2AWire tools hint at a broader marketplace but omit obvious lifecycle pieces such as listing management or job posting.

Resources