Skip to main content
Glama

List expenses and supplier bills

accounting_list_expenses
Read-onlyIdempotent

Expenses and supplier bills recorded in a period, with account, VAT, payment status and whether a slip is attached. Read-only. Needs the user's GetAccountED sign-in (they are asked to sign in the first time).

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": "accounting_list_expenses"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date YYYY-MM-DD
fromNoStart date YYYY-MM-DD
limitNoMaximum rows, 1-200 (default 50)
business_idNoAccounting practices only: which client's books (an id from accounting_list_my_businesses). Leave out to use the books chosen at sign-in.
unpaid_onlyNoOnly bills still owed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still adds real value beyond them by disclosing the authentication dependency (GetAccountED sign-in, with a first-time sign-in prompt) that an agent must anticipate before calling.

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?

Three short sentences, front-loaded with what is returned, then the read-only guarantee, then the auth prerequisite. The returned-field list is slightly compressed but nothing is redundant or padded.

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?

There is no output schema, so describing the returned fields and the optional attachment flag is genuinely needed and is present. Combined with the auth note, an agent has enough to call the tool correctly; only the relationship to the invoice-listing sibling is left unstated.

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%, so every parameter including business_id's pointer to accounting_list_my_businesses is already documented in the schema. The description's mention of a period and payment status echoes those fields but adds no format or semantics beyond them, so the baseline of 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 the resource (expenses and supplier bills), the scope (recorded in a period) and the fields returned (account, VAT, payment status, attachment). It does not explicitly distinguish itself from the nearby sibling accounting_list_invoices, which covers a parallel but different record type.

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: the period framing suggests the from/to filters, and the sign-in note tells the agent what to expect on first call. There is no explicit statement of when to prefer this over accounting_list_invoices or accounting_general_ledger, and no guidance on paging through results with limit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.