Skip to main content
Glama

List account books

list_books
Read-onlyIdempotent

Lists the user's account books (a household, a business…): id, name, currency, the user's role, whether the self-employed tax module is available, and how many months of detailed forecast the plan shows. The other tools take one of these ids as book, optional when there is only one book.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/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 the safety profile is covered. The description adds value beyond that by listing exactly what each book record exposes, which the annotations cannot convey. It stops short of describing ordering or whether archived books appear, so it is strong but not exhaustive.

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?

Two sentences, both load-bearing: the first enumerates the payload, the second explains how the ids are consumed elsewhere and the single-book exception. The parenthetical '(a household, a business…)' cheaply conveys what a book is without a paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 the description correctly carries the burden of enumerating return fields, and it does so concretely. For a zero-parameter, read-only listing tool backed by annotations, nothing an agent needs in order to call it or interpret the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to clarify beyond the empty schema. The mention of the `book` id is about output and downstream consumption rather than this tool's own inputs.

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 ('Lists the user's account books') and enumerates the returned fields: id, name, currency, role, self-employed tax module availability, and forecast months. It never names a sibling explicitly, but the note that 'the other tools take one of these ids as `book`' implicitly separates it from list_tax_documents, list_upcoming, and the get_* tools.

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 clear context for when this tool matters: its ids are the `book` argument other tools need, and that argument is optional when only one book exists. There are no explicit exclusions or 'use X instead' statements, but the positioning as the id source for every other tool is actionable guidance.

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.

Resources