View recent credits and debits (default 20, max 50). Free.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of transactions to return (max 50) | |
| api_key | No | Optional api key. Prefer X-MCP-Account header. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses no side effects, but implies a read operation. Does not explain authentication requirements despite the api_key parameter. The 'Free' note adds minimal behavioral context.
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 efficient sentences with no filler: first specifies function and constraints, second adds value ('Free'). Front-loaded and to the point.
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?
Given the simplicity of the tool and no output schema, the description covers the essential purpose and constraints. Could expand on the meaning of 'credits and debits' but overall adequate for a list tool.
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 coverage is 100% as both parameters have descriptions. The description repeats the default and max values already in the schema, adding no new semantic meaning beyond what is structured.
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?
The description clearly states it is for viewing recent credits and debits, specifying default and max limit. This distinguishes it from siblings like add_funds_* (adding funds) and get_balance (showing balance).
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 says 'Free' but provides no guidance on when to use this tool versus alternatives such as get_balance for an overall balance or add_funds for adding transactions. No prerequisites or exclusions are mentioned.
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.
Most tools have distinct purposes, but the three add_funds tools (5, 10, 20) are redundant and could be a single parameterized tool. There is also slight overlap between get_sun_times and get_weather (both provide sunrise/sunset), which may cause confusion.
Naming conventions are mixed: some tools use verb_noun (register_agent, create_wallet_setup) while others use noun_verb (get_balance, add_funds_5). There is no consistent pattern, and the presence of numbered suffixes (add_funds_5, add_funds_10) breaks uniformity.
20 tools is slightly high but reasonable for the domain. The three add_funds tools could be consolidated into one with a parameter, which would reduce clutter without losing functionality.
The tool set covers a broad range of Hawaii conditions (weather, surf, volcano, trails, ocean safety, restaurants). Minor gaps exist (e.g., tide data, specific beach alerts), but overall it provides a solid coverage for its intended purpose.