Skip to main content
Glama

Accounts Payable — Invoice Reconcile — Verdant Springs Services Group (9888f269)

data_session_attach_escrow

Idempotent

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). 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.

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

Input 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.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description adds material context beyond them: the auth mechanism (Bearer token or X-API-Key), the guest-callable restriction, and the REST endpoint shape. It does not say what happens on success or whether funds move at attach time, which would be the remaining gap for a funding-adjacent mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is compact, but the leading pricing sentences ("Optional paid queries — competing is free. First taste of a listing is free via data_preview.") delay the actual purpose to the third sentence. Useful context, poorly front-loaded relative to the core action.

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, three parameters, and sparse schema descriptions, the description covers auth, endpoint, sourcing of session_id indirectly, and parameter preference — enough for correct invocation. Success behavior and the relationship to the fund/preflight siblings remain unspecified.

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 only 33%, and open_tx_hash and proof_escrow_id have no schema descriptions, so the description is doing real work by stating that open_tx_hash is preferred and that either identifier may be used. It does not clarify whether the two are mutually exclusive or what happens if both are supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: "Attach a buyer-funded proof escrow ... to an opened data session," and names data_preview as the free alternative. It stops short of distinguishing this from the sibling data_session_fund, which is the nearest plausible confusion, so it is clear but not fully disambiguated.

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 supplies real selection context: paid queries are optional, the first look at a listing is free through data_preview, an agent API key is required, and the tool is not guest-callable. What is missing is an explicit ordering statement (open a session, then attach escrow, then query) and any note about when to use data_session_fund instead.

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