Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_get_tax_configuration

Read-onlyIdempotent

Retrieves a company's tax configuration: default tax type (IVA, IGIC, IPSI, or OTHER), percentage, exemption reason, IRPF, surcharge, and payment terms.

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.

Endpoint: GET /v1/companies/{company_id}/tax-configuration

Input Schema

TableJSON 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 establish readOnly, idempotent, openWorld, and non-destructive behavior, so the bar for additional disclosure is low. The description adds useful behavioral context beyond those hints: it states the exact endpoint and clarifies that the resource only covers company-level configuration, not the general catalogue of tax types.

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 two short paragraphs plus a one-line endpoint; every sentence earns its place. The return contents are front-loaded and the boundary note about the catalogue is a necessary scoping clarification with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description enumerates all the configuration areas an agent needs to expect in the response. The one-parameter call is fully documented by the schema, and annotations cover safety/idempotency, so nothing needed to select or invoke the tool correctly 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?

Schema coverage is 100% and the single company_id parameter already has a detailed description covering UUID format, auth/403 semantics, and header irrelevance. The tool description adds only the endpoint path, so it adds no meaning beyond the schema — 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?

The description opens with a specific verb and resource — returns the tax configuration of a company — then enumerates the exact contents (main tax, exemption reason, IRPF, surcharge, payment method/term). The boundary sentence about the tax-type catalogue living outside this resource differentiates it from catalogue-related siblings such as 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?

The description makes the tool's scope clear and explicitly warns that the tax-type catalogue is not company data and is outside this resource, which implies the right tool for catalogue lookups is elsewhere. It does not, however, name an alternative or state a when-to-use/when-not-to-use rule, leaving the router to 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