Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_get_invoice_customization

Read-onlyIdempotent

Retrieves a company's invoice rendering and delivery settings—PDF template, accent colour, invoice and email language, and current logo—stored per NIF, so you can inspect how its invoices are presented before changing them.

Instructions

Returns how the invoices of a company are rendered and delivered: PDF template, accent colour, invoice language, email language and current logo. Customization is a per-NIF property, so each company of the account carries its own.

The catalogue of available templates and suggested colours is served by GET /v1/invoice-customization-options.

BeeL API endpoint: GET /v1/companies/{company_id}/invoice-customization (reference: https://docs.beel.es)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_id": "<company_id>"
    },
    "name": "beel_get_invoice_customization"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_idYesUnique identifier (UUID) of the company the operation acts on — its identifier, not its NIF. It is the only source of context: the account that owns it is derived from it, and the `BeeL-Active-Company` header plays no part. A company you do not reach answers `403`, and so does a company that does not exist, so the existence of a company in another account is never disclosed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / company_id / description
      Previous value: -"NIF (company) the operation acts on. It is the only source of context: the account that owns it is derived from it, and the `BeeL-Active-Company` header plays no part. A NIF you do not reach answers `403`, and so does a NIF that does not exist, so the existence of a NIF in another account is never disclosed."New value: +"Unique identifier (UUID) of the company the operation acts on — its identifier, not its NIF. It is the only source of context: the account that owns it is derived from it, and the `BeeL-Active-Company` header plays no part. A company you do not reach answers `403`, and so does a company that does not exist, so the existence of a company in another account is never disclosed."
  2. First observedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent and non-destructive, so the bar is lower; the description contributes the non-obvious scoping rule that customization is stored per NIF/company rather than per account, which affects how results should be interpreted. It doesn't say what is returned when a company has never customized anything (defaults?), which is the main remaining behavioral unknown.

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 the outcome and the returned fields, then the scoping note, then the cross-reference. The 'BeeL API endpoint' line is boilerplate but functional for doc lookups; nothing is padded.

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 usefully enumerates the returned fields, which is what an agent needs to decide whether this tool answers its question. Only the absence of default/empty-state behavior and exact field naming keeps it short of fully complete for a single-parameter read.

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% and the company_id schema text is exceptionally detailed (UUID vs NIF, header is ignored, 403 masking). The description reinforces the per-company semantics of that identifier but adds no new syntax or format guidance, so the baseline 3 is appropriate.

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 ('Returns') plus the exact resource (invoice customization) and enumerates the returned facets: PDF template, accent colour, invoice language, email language, logo. The 'Returns' framing cleanly separates it from the sibling beel_update_invoice_customization, and it points at the options-catalogue endpoint that the sibling beel_list_invoice_customization_options mirrors.

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?

Gives real usage context: customization is a per-NIF property, so the caller knows to query per company rather than expect account-level settings, and it routes the caller elsewhere (`GET /v1/invoice-customization-options`) for the catalogue of templates and colours. It does not explicitly say when to choose the update tool or what to do when no customization has been set, so there is a small gap.

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

Deploy Server

Other Tools