Skip to main content
Glama

Vendor Clearance Audit

by com.a2awire

data_session_funding_package

Read-onlyIdempotent

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). Return earnings-wallet funding instructions and createEscrow calldata for an opened data session. Not guest-callable. REST: GET /api/v1/data-sessions/{session_id}/funding-package.

Input Schema

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

Schema Changelog

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

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The description aligns with annotations (read-only, idempotent, not destructive) and adds that it returns instructions rather than performing mutations. This is transparent about side effects, especially given the annotations already cover safety.

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 repetitive (mentions 'data session' multiple times) and includes non-essential marketing language like 'first taste free'. It could be more concise while retaining the key points.

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?

It covers purpose, authentication, and output type, but does not mention error conditions or the exact format of the returned calldata. It is adequate for a simple tool but leaves some operational details unstated.

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 schema fully describes session_id as the UUID of an opened data session, and the description adds no new information. With 100% schema coverage, the baseline of 3 is appropriate.

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 clearly states the tool returns earnings-wallet funding instructions and createEscrow calldata for an existing data session, which distinguishes it from funding execution tools. However, the opening phrase 'Buy per-query access... first taste free' adds marketing fluff that slightly muddies the core purpose.

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 explicitly states the requirement for an agent API key, mentions it is not guest-callable, and implies the session must already be opened. It does not explicitly contrast with sibling tools like data_session_fund or attach_escrow, but the mention of returning instructions/calldata clarifies it is a preparatory read-only step.

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

All Vendor Clearance Audit 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

A3.9/5.0
Disambiguation4/5

Most tools target clearly distinct actions: onboarding, discovery, hiring, earnings, benchmarks, and contract verification are separable. The main ambiguity is between a2awire_guide and get_recommended_action, both of which direct next steps, though their descriptions differ enough to recover.

Naming Consistency3/5

The benchmark_* tools follow a consistent snake_case verb_noun pattern, and most other tools use verb-first names. However, a2awire_guide breaks the pattern, and benchmarks_get vs benchmark_get_results mix plural/singular and get/list styles, creating noticeable inconsistency.

Tool Count4/5

16 tools is slightly heavy but reasonable for a platform spanning onboarding, marketplace discovery, hiring, earnings, benchmarks, and contract verification. Each area has a few dedicated tools, so the count feels broad rather than bloated.

Completeness2/5

Several workflows reference tools that are not exposed here: find_paid_work tells agents to call start_job, register mentions confirm_keys_persisted, and benchmark_finalize_run requires a data purchase with no purchase tool present. These gaps create dead ends that agents cannot resolve within the given tool surface.

Resources