Skip to main content
Glama

Get Bookkeeping Vendors

get_bookkeeping_vendors
Read-only

Lists the vendors the company pays, as doola Bookkeeping keeps them. statuses filters them, comma-separated; omit it for ACTIVE and PENDING. When bookkeepingSetUp is false there are no books to read yet. If includedInPlan is true, bookkeeping is already in the user's doola plan: never offer it, share setUpLink where they set it up, or with no setUpLink point them to doola support. Otherwise follow nextStep to offer doola Bookkeeping. Answer in plain language and never show the user the field names. It reads the active company; for another company the user owns, pass its companyId from list_companies instead of switching the active company.

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

Input Schema

NameRequiredDescriptionDefault
contextNoOptional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details.
statusesNocomma-separated statuses (e.g. ACTIVE,PENDING)
companyIdNoOPTIONAL. The doolaCompanyId (an id like '30E5c1AQA326uOuDlsic4No7zZ5'). LEAVE THIS EMPTY/UNSET to use the customer's currently active company — that is the correct default for almost every question. Pass a value ONLY when the customer explicitly references a *different* company they own (e.g. 'show me transactions for my other company X'). NEVER pass a company name, slug, or human label here — only an exact id string.
llm_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
conversation_idNoOptional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, but the description goes well beyond that: it discloses response-field-driven branching (bookkeepingSetUp, includedInPlan, setUpLink, nextStep), the status default, and the active-company read scope. It even specifies presentation constraints (plain language, never expose field names), which is behavioral guidance an agent cannot get from annotations.

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?

Front-loaded with purpose, then gating conditions, then cross-company routing — a logical order with no filler sentences. The opening clause "as doola Bookkeeping keeps them" is slightly awkward, but every subsequent sentence carries operational content.

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 does the work of explaining the meaningful response fields behaviorally (bookkeepingSetUp, includedInPlan, setUpLink, nextStep) and the company-scoping model. It stops short of describing what a vendor record itself contains (name, id, status), which is the one gap for a list-returning tool.

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?

Schema coverage is 100%, so the schema carries most of the weight, but the description adds real meaning: the default status set when statuses is omitted (not stated in the schema) and the rule that a foreign companyId should come from list_companies rather than from switching the active company. It adds less for the analytics-only params, which the schema already explains fully.

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?

States a specific verb and resource ("Lists the vendors the company pays") plus the owning subsystem (doola Bookkeeping), which cleanly separates it from siblings like get_bookkeeping_clients, get_bookkeeping_transactions, and get_bookkeeping_bank_accounts. An agent can identify the tool without opening the schema.

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

Usage Guidelines5/5

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

Explicitly covers the filter default ("omit it for ACTIVE and PENDING"), the preconditions ("When bookkeepingSetUp is false there are no books to read yet"), the upsell branch ("If includedInPlan is true ... never offer it"), and the fallback path ("Otherwise follow nextStep"). It also routes cross-company requests to list_companies for the companyId rather than switching the active company, naming the alternative directly.

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.