Skip to main content
Glama
Sign In
freeagent-mcp-server

freeagent-mcp-server

by samaxbytez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

freeagent_update_bank_account

Destructive

Update an existing FreeAgent bank account's name, bank name, or primary status by supplying its account ID.

Instructions

Update an existing bank account in FreeAgent

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bank_account_id": "<bank_account_id>"
    },
    "name": "freeagent_update_bank_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName for the bank account
bank_nameNoName of the bank
is_primaryNoWhether this is the primary account
bank_account_idYesThe ID of the bank account to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.3.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a mutating, potentially destructive write. The description adds nothing beyond that: no warning about which changes are irreversible, no auth or permission context, and crucially no disclosure of partial-update semantics (whether omitting 'is_primary' clears or preserves the existing value).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of waste, but its brevity comes at the cost of under-specification rather than genuine efficiency. There is room for one more sentence on update semantics without bloat.

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?

For a destructive mutation tool with four parameters and no output schema, the description should at minimum clarify partial-update behavior and any side effects (e.g., promoting an account to primary). Annotations cover the safety profile and the schema covers fields, but the semantic gaps around mutation behavior remain unfilled.

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%, so every parameter (name, bank_name, is_primary, bank_account_id) is already documented in the schema. The description contributes no additional meaning such as validation rules, constraints on setting is_primary, or the ID format. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource pair ('Update an existing bank account') is specific about the action and object, but the description is essentially a restatement of the tool name with only the word 'existing' added. It does not distinguish this from siblings like freeagent_get_bank_account or freeagent_delete_bank_account beyond what the name already conveys.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus freeagent_list_bank_accounts / freeagent_get_bank_account (to find the ID first) or freeagent_delete_bank_account. No prerequisites, no note that only fields supplied are changed, no mention of what happens to omitted fields.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools