Skip to main content
Glama

agent-bank

by io.github.WirterNow

update_settings

Update or retrieve an agent's settings. Requires api_key for updates. Use action='get' to retrieve (no api_key needed).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNo'update' (default) or 'get'
api_keyNoYour api_key (required for updates)
agent_idYesUUID of the agent
settingsNoNested settings object (alternative to flat params)
auto_yieldNoEnable automatic yield optimization
max_daily_spendNoMaximum daily spend limit in USDC (alias: daily_spend_limit)
max_spend_per_txNoAlias for max_single_transaction_spend
preferred_tokensNoPreferred token symbols
daily_spend_limitNoAlias for max_daily_spend
notification_webhookNoWebhook URL for notifications
max_single_transaction_spendNoMaximum single transaction limit in USDC (alias: max_spend_per_tx)

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so description bears full burden. It discloses the dual behavior and auth requirement but does not mention side effects (e.g., if updates are immediate, if previous settings are overwritten), rate limits, or output format.

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, front-loaded with purpose, no unnecessary words. Very efficient communication.

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?

Missing output schema, and description does not explain return values. Also does not clarify the relationship between flat parameters and the nested settings object, nor mention aliases (e.g., max_daily_spend and daily_spend_limit). Incomplete for full understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all parameters, but description adds context by clarifying conditional requirement for api_key based on action. This goes beyond schema descriptions, aiding correct invocation.

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 states 'Update or retrieve an agent's settings', clearly specifying two actions. It adds nuance beyond name which suggests only update. Not a tautology, but could be more specific about the scope of settings.

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?

Explicitly says when to use 'get' vs 'update' and that api_key is required for updates. Provides basic usage context but does not compare to sibling tools or state when not to use this tool.

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