increase_get_transactionRetrieve a single transaction by id. Increase API: GET /transactions/{transaction_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| transaction_id | Yes | Transaction id (e.g. transaction_...). |
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?
Annotations already declare readOnlyHint=true. Description adds API endpoint method but no additional behavioral traits like auth or rate limits.
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, no fluff, front-loaded with action and resource.
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?
Lacks return value description and error cases. Adequate for a simple get tool but could be more complete.
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 description coverage is 100% with example. Description does not add meaning beyond what 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?
Clear verb 'retrieve' with resource 'a single transaction by id', distinguishes from list tools. API endpoint explicitly stated.
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?
Implied usage when you have a transaction_id, but no explicit guidance on when to use this vs. other get tools like get_account. Sibling tools not 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.
Each tool targets a distinct resource type (account, account number, ACH transfer, etc.) with clear verb_noun naming, making them easily distinguishable.
All tools follow a consistent `increase_verb_noun` pattern in snake_case, with verbs like create, get, list, lookup.
18 tools is slightly above the typical 3-15 range, but the scope of banking operations (accounts, transfers, transactions, cards, entities) justifies the count.
The server is heavily read-only with only one mutation (create_external_account). Missing create/update/delete for accounts, transfers, cards, etc., which limits its usefulness for full banking workflows.