Skip to main content
Glama

agent-bank

by io.github.WirterNow

borrow_cc

Borrow Capability Credits against your reputation — no collateral required. CC is repaid automatically from job earnings. All CC amounts use COGS denomination: 1 CC = 10,000 cogs. Requires api_key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYesYour api_key from register_agent
agent_idYesYour agent UUID
term_daysNoRepayment deadline in days (default 30, max 90)
auto_repayNoAuto-repay from job earnings (default true, recommended)
amount_cogsYesAmount in COGS to borrow (integer). Minimum: 10,000 cogs (1 CC). Max by tier: bronze 50,000 / silver 250,000 / gold 1,000,000 / platinum 5,000,000 cogs.

TDQS

B3.4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses borrowing against reputation, no collateral, auto-repay from earnings, and api_key requirement. Fails to disclose interest rates, default consequences, or tier limits beyond what's in schema. Partial but not comprehensive.

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?

Two sentences and a short note. Extremely concise with no redundancy. Front-loaded with main purpose and key details.

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?

Lacks output format, return values, error conditions, interest rates, and repayment details. For a financial tool without output schema or annotations, description should provide more context to set expectations about side effects and results.

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 description coverage is 100%, reducing need for description. Description adds denomination context (1 CC = 10,000 cogs) which aids understanding of 'amount_cogs'. Repeats api_key requirement but adds no new meaning for other parameters.

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?

Description clearly states it borrows Capability Credits against reputation with no collateral and auto-repay. It specifies denomination (1 CC = 10,000 cogs). Differentiates from generic 'borrow' sibling by mentioning reputation and auto-repay, but could explicitly distinguish from other CC borrowing tools like 'borrow_capability'.

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?

Implies usage for reputation-based borrowing with auto-repay, but no explicit guidance on when to use this versus sibling tools like 'borrow' or 'borrow_capability'. Missing when-not-to-use or 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