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

freeagent-mcp-server

by samaxbytez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

freeagent_get_trial_balance

Read-only

Retrieve a FreeAgent trial balance summary, optionally filtered by date range, to review account balances and check debit and credit totals.

Instructions

Get the trial balance summary from FreeAgent with optional date range filtering

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

Input Schema

NameRequiredDescriptionDefault
to_dateNoEnd date for the trial balance in YYYY-MM-DD format
from_dateNoStart date for the trial balance in YYYY-MM-DD format

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.2/5.0
Behavior3/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 only that date filtering is optional; it says nothing about what the summary contains (per-account debit/credit balances), what happens when dates are omitted, or how large the result may be.

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 no filler; the resource is stated before the optional modifier. It is efficient, though it is arguably too terse given the ambiguity with the opening-balances sibling.

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?

With only two optional parameters, no output schema, and annotations covering safety, the definition is minimally adequate for calling the tool. However, it leaves the agent guessing about the default reporting period when no dates are supplied and about the shape of the returned trial balance, which matters for a financial report tool.

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 both from_date and to_date are already documented with format (YYYY-MM-DD) and meaning. The description merely restates 'optional date range filtering' without adding semantics such as whether both bounds are inclusive or what the default range is, so the 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?

The description names a specific verb ('Get') and resource ('trial balance summary') and identifies the source system (FreeAgent). It is clear on its own, but it does not distinguish itself from the closely related sibling freeagent_get_trial_balance_opening, which an agent could easily confuse with this tool.

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?

The only usage signal is 'with optional date range filtering', which implies you may scope the report by period. There is no statement of when to prefer this over freeagent_get_trial_balance_opening, freeagent_get_balance_sheet, or freeagent_get_opening_balances, and no mention of prerequisites or exclusions.

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