Skip to main content
Glama

agent-bank

by io.github.WirterNow

estimate_cc_price

Estimate how many cogs (CC sub-unit) to pay for a task. Returns recommended_cogs (integer) and recommended_cc. 1 CC = 10,000 cogs. Use BEFORE posting a job or accepting an offer. 1 CWU = F(1,000,003) mod (10⁹+7) = 986,892,585.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idNoOptional — your agent UUID for personalized market context
task_typeYesType: code_review, research, data_analysis, debugging, writing, translation, simple_qa, other
task_descriptionNoBrief description of the work
estimated_minutesYesEstimated compute/work time in minutes

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so description bears full responsibility. It reveals return types but not how the estimate is computed, whether it uses market rates, or assumptions. The CWU line adds irrelevant and unexplained information.

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

Conciseness2/5

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

Short but includes an irrelevant, unexplained line about CWU that distracts. Front-loads purpose well but the extra line harms conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so description should explain return values more thoroughly. Does not mention how estimation works, assumptions, or limitations. The CWU line is incomplete and irrelevant.

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 covers 100% of parameters with descriptions. The description adds nothing beyond the schema, so baseline 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?

Clearly states it estimates the payment in cogs/CC for a task, specifying when to use (BEFORE posting a job or accepting an offer). The irrelevant CWU line is confusing but does not obscure 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?

Explicitly mentions 'Use BEFORE posting a job or accepting an offer.' No alternative tools are mentioned, but the context makes the usage clear.

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