billy-mcp

list_daybooks

Read-only

Retrieve daybooks from Billy accounting to locate the daybook ID needed for manual journal entries.

Instructions

List daybooks in Billy. Find the daybook ID used for manual journal entries.

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

Input Schema

Name	Required	Description
`page`	No	Page number (1-based)
`verbose`	No	Return the full Billy response. Default false: compact records with key fields only (saves ~90% context)
`pageSize`	No	Records per page (max 1000, default 50)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 8, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already mark this as read-only. The description does not add extra behavioral details beyond what annotations provide, but it does not contradict them.

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?

The description is concise with two sentences that are directly to the point, no extraneous information.

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?

For a simple listing tool with good annotations, it provides enough context (purpose and use case). However, it does not explain return values since no output schema is present, but the implication is clear.

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 covers all 3 parameters with descriptions. The tool description adds no additional parameter-specific information, so baseline score applies.

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 tool lists daybooks in Billy and specifies the use case of finding the daybook ID for manual journal entries, distinguishing it from other list 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 provides a specific use case (finding daybook ID for manual journal entries) but does not explicitly state when not to use it or differentiate from other list tools like list_daybook_transactions.

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