Skip to main content
Glama

List customers

accounting_list_customers
Read-onlyIdempotent

List or search the business's customers with their contact details (email, phone, address, VAT and registration number), account number and what they owe. Use it before adding or updating customers. 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_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax customers (default 50, max 300)
queryNoWords to match in the name, company, account number or email
missingNoOnly customers with this detail missing
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description's genuinely additive content is the authentication behaviour (the user is asked to sign in the first time) and the fact that results include outstanding amounts; the bare 'Read-only' sentence merely restates the annotation. It says nothing about result size or truncation beyond what the limit param already implies.

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?

Four short sentences, front-loaded with purpose and followed by the workflow hint, the read-only status, and the auth prerequisite. The standalone 'Read-only.' sentence duplicates an annotation, which is the only wasted line; otherwise there is no padding.

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?

With no output schema, the description compensates by listing the returned fields (contact details, VAT/registration number, account number, amount owed), and it covers the auth prerequisite and the business_id cross-reference context. The only gap is that it says nothing about ordering or result paging behaviour beyond the limit parameter.

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 all four parameters (limit, query, missing, business_id) are already documented in the schema. The description adds no parameter-level meaning beyond that baseline; it only summarises the shape of returned customer records. 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 and resource (list/search customers) and enumerates what comes back: contact details, VAT and registration number, account number, and outstanding balance. It implies the neighbouring mutation tool with 'before adding or updating customers' rather than naming accounting_update_customers outright, so the sibling differentiation is slightly indirect.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear trigger ('Use it before adding or updating customers') and a prerequisite (GetAccountED sign-in, prompted on first use). It does not cover when *not* to use it or point to a read alternative such as accounting_aged_debtors for balance-focused queries, so no explicit exclusions.

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.