Skip to main content
Glama

E-Commerce — Refund Request Audit — Kestrel Outfitters (2b20046e)

data_session_fund

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). Platform-execute funding for the session_id from data_session_open when the buyer is a testnet sandbox wallet the platform holds a key for (approve + createEscrowWithProof + attach). Testnet only; an attached session returns without re-funding. During the wallet rebuild it answers a structured wallet_rebuild_paused; self-sign via data_session_funding_package still works. Not guest-callable. REST twin: POST /api/v1/data-sessions/{session_id}/fund-sandbox. Next: data_session_query (sandbox_receipt=true).

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

Input Schema

NameRequiredDescriptionDefault
session_idYesUUID of a data session you opened (from data_session_open).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses required auth (Bearer or X-API-Key), testnet-only scope, guest-callability restriction, idempotent short-circuit when already attached, and the special 'wallet_rebuild_paused' structured response during rebuild. The annotations cover the safety profile, and the description adds the operational context an agent needs to predict outcomes.

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?

A single dense paragraph where nearly every clause carries actionable information (auth, condition, idempotency, paused state, REST twin, next step). It is somewhat jargon-heavy and the opening pricing sentence is context rather than tool behavior, but there is little pure filler.

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 one-parameter mutation with no output schema, it covers the important outcomes: the no-op when already attached and the structured 'wallet_rebuild_paused' response, plus the natural next call. Error handling beyond the rebuild case and the shape of a successful receipt are left implicit.

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?

With a single parameter at 100% schema coverage, the schema already fully documents session_id. The description adds only the provenance hint ('from data_session_open'), which duplicates what the schema field description already says. Baseline 3 is appropriate when the schema does the work.

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?

States a specific verb and resource ('Platform-execute funding for the session_id') and scopes it precisely to the case where the buyer is a testnet sandbox wallet the platform holds a key for. It also implicitly distinguishes itself from the self-sign path by naming 'approve + createEscrowWithProof + attach' as the mechanism. It stops short of a crisp one-line 'this funds X' opener, since the first sentence is about pricing context rather than the tool itself.

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?

Gives an explicit precondition ('when the buyer is a testnet sandbox wallet the platform holds a key for') and points to the alternative for the other case ('self-sign via data_session_funding_package still works'). It also states the terminal behavior for already-attached sessions and the follow-up call ('Next: data_session_query'). It does not spell out a general when-not-to-use list beyond the sandbox-wallet condition.

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