Skip to main content
Glama
samaxbytez

freeagent-mcp-server

by samaxbytez

freeagent_list_bills

List bills from FreeAgent with filtering options by view, date, contact, or project to manage accounting records.

Instructions

List bills from FreeAgent with optional filtering by view, date range, contact, or project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoFilter bills by view
from_dateNoFilter bills from this date (YYYY-MM-DD)
to_dateNoFilter bills to this date (YYYY-MM-DD)
updated_sinceNoOnly return bills updated since this ISO 8601 date
contactNoFilter by contact URL
projectNoFilter by project URL
nested_bill_itemsNoWhether to include nested bill items in the response
Behavior2/5

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

No annotations provided, so the description carries full burden. It only states listing with filters, omitting details on pagination, sorting, default behavior, or error responses.

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?

Single, front-loaded sentence with no redundant words. Efficiently conveys core functionality.

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?

Given 7 parameters and no output schema/annotations, the description lacks details on return format, pagination, or performance implications, making it incomplete for an AI agent.

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 coverage is 100% with parameter descriptions. The description adds no extra meaning beyond summarizing the filters, so a baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the action (list) and resource (bills) with specific filtering options (view, date range, contact, project), distinguishing it from sibling tools like freeagent_get_bill.

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?

No explicit instructions on when to use this vs. alternatives like freeagent_get_bill or other list tools, but the description implies its purpose for listing with optional filters.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/samaxbytez/freeagent-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server