Skip to main content
Glama
Buchhaltungsbutler MCP

Buchhaltungsbutler MCP

Cost Locations: get cost locations

cost_locations_list
Read-onlyIdempotent

Retrieves cost locations for a customer account to identify available cost centres for cost_location fields in posting tools. Read-only; returns up to 1,000 rows.

Instructions

🟢 READ-ONLY: Fetches data. Makes no changes to the accounting records.

get cost locations

Get cost locations for a specified customer account. The response includes the number of returned rows and an array of cost locations data. NOTE: Each request is limited to 1000 cost locations!

Use to list the cost centres available for the cost_location fields on the posting tools.

Endpoint: POST /cost-locations/get

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

Input Schema

NameRequiredDescriptionDefault
codeNoThe code of one specific cost location. If provided, only the cost location with this code will be returned.
limitNoSet a limit of returned postings. NOTE: the maximum limit is 1000!
offsetNoSet an offset for the returned postings.

Output Schema

NameRequiredDescriptionDefault
dataNoAn array of cost locations data
rowsNoNumber of returned rows
messageNoblank
successYesSuccess boolean

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.5
    • changedOutput schema / properties / data / items / properties / code / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / data / items / properties / name / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  2. Addedv1.1.2

TDQS

A4.1/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 description isn't carrying the safety burden. It still adds genuine context beyond them: the 1000-row hard cap per request and the response shape (row count plus array of cost locations). It does not explain sorting, pagination defaults, or error behavior, keeping it below a 5.

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-loads the read-only signal, then purpose, then the limit constraint, then the endpoint — a sensible order. Some redundancy remains: the title is repeated verbatim as a bolded line and the read-only claim is restated, so a sentence or two could be trimmed.

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 only three optional params, full schema coverage and an output schema, the description is close to complete; it explains the cap and the return shape. The unexplained 'specified customer account' scope leaves a small gap about what the tool actually filters on.

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 the baseline is 3 and the schema already explains `code`, `limit` and `offset`. The description only echoes the 1000 limit already documented in the schema, and its phrase 'for a specified customer account' implies a scope parameter that does not exist in the schema, which slightly muddies rather than clarifies.

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 ('Get cost locations'), scopes it ('for a specified customer account'), and distinguishes it from the cost_locations_create/update/delete siblings implicitly by being a fetch operation. An agent can immediately tell this is the read-side listing counterpart.

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?

Explicitly says what it's for: 'Use to list the cost centres available for the `cost_location` fields on the posting tools' — that is real routing guidance toward a downstream use case. It stops short of naming exclusions or explaining when to filter by `code` versus paging, so not a 5.

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