Skip to main content
Glama
freeagent-mcp-server

freeagent-mcp-server

by samaxbytez

freeagent_list_bank_accounts

Read-only

List FreeAgent bank accounts and filter by standard bank, credit card, or PayPal account type, with pagination for retrieving all results.

Instructions

List bank accounts from FreeAgent with optional view filter

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "freeagent_list_bank_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number to fetch (default 1)
viewNoFilter bank accounts by type
per_pageNoResults per page (default 25, max 100). Check pagination.next_page in the response for more results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Page number to fetch (default 1)",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / per_page
      Added value: +{
      +  "description": "Results per page (default 25, max 100). Check pagination.next_page in the response for more results.",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. First observedv1.3.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that beyond repeating the view-filter concept from the schema — no note on result ordering, pagination limits, or whether inactive/closed accounts are included. For a simple read tool this is tolerable but it contributes no behavioral context of its own.

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

Conciseness4/5

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

A single front-loaded sentence with zero filler, which is appropriate for a low-complexity list endpoint. It is efficient, though its brevity is part of why usage and pagination context are absent.

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

Completeness3/5

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

For a read-only list tool with 100% schema coverage and no required parameters, the definition plus annotations and schema give an agent enough to call it correctly. It remains only minimally complete: nothing explains what a returned account contains or how the enumerated views map to real account types, which the absent output schema would otherwise have had to cover.

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%, with all three parameters documented (page default 1, per_page default 25/max 100 with a pointer to pagination.next_page, and an enumerated view filter), so the baseline is 3. The phrase "optional view filter" merely restates what the schema already says and adds no syntax or semantic detail.

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 pairs a specific verb ("List") with a specific resource ("bank accounts") and names the source system (FreeAgent), so an agent can immediately distinguish it from freeagent_get_bank_account, update_bank_account, and delete_bank_account. It stops short of an explicit sibling call-out, but the verb choice itself removes most ambiguity.

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?

Usage is only implied by the verb: use this to enumerate accounts, use freeagent_get_bank_account for a single record. There is no explicit when-to-use/when-not statement, no mention of when the view filter should be applied versus fetching everything, and no prerequisites (e.g. authentication or company scoping) are stated.

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