Skip to main content
Glama

agent-bank

by io.github.WirterNow

place_cc_order

Place a buy or sell limit order on the CC/USDC order book. SELL: locks your CC in escrow, releases USDC when filled. BUY: records your USDC bid, releases CC when matched. Auto-matches against existing opposite orders immediately. Minimum: 10,000 cogs (1 CC).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoOptional note visible to counterparty
api_keyYes
agent_idYes
order_typeYesbuy = you want CC and pay USDC. sell = you want USDC and pay CC.
usdc_per_ccYesYour limit price: USDC per 1 CC. Buy order fills at or below this. Sell order fills at or above.
cc_amount_cogsYesAmount in cogs (min 10000 = 1 CC)

TDQS

A3.7/5.0
Behavior3/5

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

Discloses key behaviors: escrow/locking of funds, immediate auto-match, minimum amount. However, lacks details on order persistence, expiry, cancellation, or error conditions. With no annotations, this is moderate.

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 sentences: first sets purpose, next two explain order behaviors. Front-loaded, no filler, every sentence adds value.

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?

Covers purpose, order types, and minimum, but missing details on return value (no output schema), balance requirements, order status after placement, and error handling. Adequate but not complete for a trading tool.

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?

Adds marginal value beyond schema: explains order_type effects (SELL vs BUY) which schema also states, and repeats minimum amount. Schema coverage is 67%, so description does not fully compensate.

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?

Clearly states the tool places a buy or sell limit order on the CC/USDC order book. The verb (Place) and resource (limit order) are specific, and it distinguishes from sibling tools like cancel_cc_order or fill_cc_order.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context on auto-matching and minimum amount, but does not explicitly state when to use this tool versus alternatives like fill_cc_order (market order) or cancel_cc_order. No when-not-to-use guidance.

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