Request a deposit into a Gitbank vault. Returns a confirm_code the user must post on GitHub to authorize execution. Supported tokens: USDC, WETH.
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | Token symbol: USDC or WETH | |
| amount | Yes | Amount to deposit | |
| github_username | Yes | GitHub username of the vault owner |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds critical behavioral context beyond annotations: the tool is non-destructive but requires external authorization via GitHub. The openWorldHint annotation is aligned, and the two-step process is clearly communicated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the primary action and return value. Every sentence adds value, no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool complexity is low with three parameters fully described. The description covers the main flow and return type. Minor gap: it doesn't mention prerequisites like vault existence, but the schema's github_username requirement implies it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers all three parameters with descriptions (100% coverage). The description adds only the supported token list, which is already partially in the schema. No additional semantic value beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the action ('Request a deposit into a Gitbank vault') and the return value ('Returns a confirm_code the user must post on GitHub to authorize execution'). It distinguishes well from sibling tools like request_withdraw and request_transfer.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description specifies supported tokens (USDC, WETH) and implicitly that this tool is for initiating deposits. However, it could explicitly contrast with related tools (e.g., request_withdraw) to provide stronger guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: informational gets/lists, action-oriented requests with confirm_code, and a status checker. No two tools overlap in function; e.g., get_stock_price vs get_rwa_portfolio differentiate price vs holdings.
All tool names follow a consistent verb_noun pattern: get_ for retrieval, list_ for enumeration, request_ for actions requiring authorization, and check_ for status. No mixed conventions or vague verbs.
16 tools cover the full scope of Gitbank's functionality—viewing balances, portfolios, prices, transactions, and initiating deposits, withdrawals, swaps, stock trades, bounty assignments, and token launches. The count is well-proportioned for a complex financial/project management server.
The tool set provides comprehensive coverage for querying and initiating actions, but lacks a tool to cancel pending requests or to directly confirm actions (confirmation happens externally via GitHub). Minor gap, but core workflows are supported.
