Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_get_tax_configuration

Read-onlyIdempotent

Retrieve a company’s tax settings by company ID, including default tax type, percentage, regime, exemption reason, IRPF, surcharge, and payment terms for compliant invoicing.

Instructions

Returns the tax configuration of a company: its default main tax (IVA, IGIC, IPSI or OTHER) with the default percentage and regime key, the default exemption reason, its IRPF and equivalence surcharge settings, and the default payment method and payment term.

The catalogue of tax types this configuration draws from is not company data and lives outside this resource.

BeeL API endpoint: GET /v1/companies/{company_id}/tax-configuration (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_tax_configuration"
  }
}

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by describing the composition of the returned configuration in detail (which matters since there is no output schema) and by citing the concrete endpoint GET /v1/companies/{company_id}/tax-configuration plus a docs reference. It stops short of mentioning auth/permission requirements or error behavior beyond what the schema already documents.

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?

The payload description is front-loaded and the catalogue-boundary note follows logically, with the endpoint reference last. The enumerated field list is dense but each item is meaningful; the parenthetical list of tax types and the docs URL are the only mildly expendable elements.

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 carries the burden of explaining return values, and it does so thoroughly by enumerating the configuration fields. Combined with the schema's error semantics and the annotations' safety hints, an agent has enough to call this correctly; only explicit routing to the update/catalogue siblings is missing.

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?

There is a single parameter with 100% schema description coverage, and that schema text is unusually rich (UUID format, identifier-not-NIF, 403 non-disclosure semantics). The description adds nothing about company_id, so the baseline of 3 applies — the schema does all the parameter work.

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 names a specific verb and resource ("Returns the tax configuration of a company") and then enumerates exactly what the payload contains: default main tax among IVA/IGIC/IPSI/OTHER with percentage and regime key, default exemption reason, IRPF and equivalence surcharge settings, default payment method and payment term. That level of specificity distinguishes it cleanly from siblings like beel_get_verifactu_configuration or beel_list_tax_types.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the note that the tax-type catalogue "lives outside this resource" steers the agent toward beel_list_tax_types, but it never names that sibling or says explicitly when to call this tool versus beel_update_tax_configuration. There are no exclusions or prerequisites spelled out, so an agent must infer the boundary.

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