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

freeagent-mcp-server

by samaxbytez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

freeagent_get_bank_account

Read-only

Retrieve a single FreeAgent bank account by ID to access its details for reconciliation, reporting, or account management.

Instructions

Get a single bank account from FreeAgent by ID

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_get_bank_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
bank_account_idYesThe ID of the bank account to retrieve

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

B3.4/5.0
Behavior2/5

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

The annotations already establish readOnlyHint=true and openWorldHint=false, while the description adds little behavioral information beyond scoped retrieval. It does not address missing-account behavior, permissions, rate limits, or other operational traits, though it does not contradict the annotations.

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?

One short, front-loaded sentence communicates the operation, resource, service, and lookup key without filler. Its brevity is appropriate for a simple getter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read, the description, schema, and annotations provide enough information for basic selection and invocation. It remains minimal because there is no output schema, ID-discovery guidance, or explanation of behavior when the account does not exist.

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?

The sole bank_account_id parameter is fully documented in the schema, including its required status, type, pattern, and purpose, so the high-coverage baseline applies. The description repeats that retrieval is by ID without adding identifier semantics or explaining where to obtain the ID.

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?

The description gives a specific verb and resource—getting one FreeAgent bank account—and “by ID” clarifies the lookup scope. It broadly differs from list and mutation siblings, but does not explicitly contrast freeagent_list_bank_accounts or freeagent_get_bank_transaction.

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?

“A single bank account … by ID” implies use when the caller already knows an account ID and wants one record. It provides no explicit routing to freeagent_list_bank_accounts for discovering accounts or finding an ID, and no other when-to-use or when-not-to-use guidance.

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