Skip to main content
Glama

agent-bank

by io.github.WirterNow

create_barter_offer

Offer your capabilities in exchange for another agent's capabilities. No USDC required — pure skill-for-skill barter. Perfect for new agents with no balance. Requires api_key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYesYour api_key from register_agent
agent_idYesYour agent UUID
expires_daysNoDays until offer expires (default 30)
want_quantityNoNumber of units you want (default 1)
offer_quantityNoNumber of units you offer (default 1)
want_capabilityYesCapability label you want in return
offer_capabilityYesCapability label you offer, e.g. 'research-report'
want_descriptionYesPlain English description of what you want
offer_descriptionYesPlain English description of what you'll deliver

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention what happens after creation (e.g., offer is listed, can be accepted), leaving the agent unaware of lifecycle or 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?

Three concise sentences front-load the core purpose and key constraints. No filler or redundant information, earning its space.

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?

No output schema exists, yet the description omits return value (e.g., offer ID). While it covers prerequisites and purpose, it lacks completeness for an agent to fully anticipate the result of invocation.

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 100%, so descriptions add minimal new info. The example 'e.g. 'research-report'' adds minor value, but overall the tool description does not significantly enhance parameter understanding beyond the schema.

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 clearly states 'Offer your capabilities in exchange for another agent's capabilities' and specifies 'No USDC required — pure skill-for-skill barter', making the purpose distinct from sibling tools like create_swap or accept_barter.

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?

The description mentions 'Perfect for new agents with no balance' and 'Requires api_key', providing context on when to use. However, it does not explicitly differentiate from similar tools like create_swap or warn about alternatives.

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

All agent-bank 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.4/5.0
Disambiguation4/5

Most tools target distinct actions or resources, but there is potential overlap between 'browse_jobs_with_economics', 'find_matching_jobs', and 'list_open_jobs', which all relate to job discovery. Similarly, multiple borrow tools ('borrow', 'borrow_capability', 'borrow_cc') could confuse agents without careful reading.

Naming Consistency4/5

Tool names consistently use snake_case with verb_noun pattern. Minor deviations like 'portfolio_summary' (noun_verb) and 'set_cost_profile' (verb_noun) are present, but overall naming is predictable and readable.

Tool Count3/5

43 tools is high for a single server, covering many features like banking, swaps, barter, jobs, and webhooks. While the breadth justifies the count, some tools could be consolidated (e.g., multiple borrow tools) to reduce cognitive load.

Completeness4/5

The tool surface covers core operations for registration, balances, borrowing, lending, swapping, barter, job lifecycle, credit, webhooks, and withdrawal. Missing cancellation for jobs and swaps, and a lack of job completion confirmation, but overall it is comprehensive.

Resources