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

freeagent-mcp-server

by samaxbytez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

freeagent_list_bank_transactions

Read-only

List bank transactions for a specific FreeAgent bank account, with optional date, view, and pagination filters to review or reconcile account activity.

Instructions

List bank transactions from FreeAgent for a specific bank account

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": "<bank_account>"
    },
    "name": "freeagent_list_bank_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number to fetch (default 1)
viewNoFilter transactions by view
to_dateNoEnd date for filtering (YYYY-MM-DD)
per_pageNoResults per page (default 25, max 100). Check pagination.next_page in the response for more results.
from_dateNoStart date for filtering (YYYY-MM-DD)
bank_accountYesThe full URL of the bank account to list transactions for
updated_sinceNoOnly return transactions updated since this ISO 8601 date

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

C2.9/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 safety is covered structurally. The description adds only the requirement of scoping to one bank account, and says nothing about pagination behavior, result volume, or that results are paginated by default at 25 per page — all useful context for a list endpoint that an agent must plan around.

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 short sentence with no filler and the key constraint front-loaded. It is efficient, though its brevity is under-specification rather than disciplined compression.

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 7-parameter read-only list tool with no output schema, the description is only minimally adequate: an agent must read the schema to discover filtering and pagination options. It does not mislead, but it leaves the caller to reconstruct the retrieval strategy entirely from structured fields.

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% and every parameter (page, per_page, view, from_date, to_date, updated_since) is documented in the schema itself, including enum values and the pagination hint. The description adds nothing beyond restating the required bank_account scoping, so baseline 3 applies.

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?

States a clear verb ('List') and resource ('bank transactions') plus the required scope ('for a specific bank account'). This distinguishes it from the singular freeagent_get_bank_transaction and from freeagent_list_bank_accounts without needing the schema.

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?

There is no guidance on when to use this versus freeagent_get_bank_transaction, nor any mention of when filtering by view or date range is appropriate. The only implied usage is that a bank account URL must already be known, which is left for the agent to infer.

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