BeeL MCP server

Official

Overview Schema Source Related Servers Discussions Admin

beel_get_verifactu_configuration

Read-onlyIdempotent

Retrieves a company's VeriFactu configuration by company UUID so you can check whether its NIF can issue compliant Spanish e-invoices before creating any invoice.

Instructions

Retrieves the VeriFactu configuration of this company. The configuration belongs to the NIF, so the NIF in the path is what decides which one is returned.

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

⚠️ Read before calling:

How to tell, before issuing, whether a NIF can issue, and what each blocker means. (resource: beel://guardrails/verifactu-gates)

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_verifactu_configuration"
  }
}

Input Schema

Name	Required	Description	Default
`company_id`	Yes	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.5.0Aug 30, 2026

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."

First observedv0.3.1Aug 25, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already cover the full safety profile (readOnlyHint, idempotentHint, openWorldHint=false, destructiveHint=false), so the description only needs to add context. It contributes the NIF-keyed nature of the configuration and a pointer to pre-issuance gate documentation, which is genuinely useful, but it does not say what the configuration contains or how a disabled/unconfigured state presents itself.

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?

Two compact paragraphs: identity of the resource first, then a warning block, which is a sensible front-loading. The endpoint and docs URL are mildly redundant with the tool name but serve as useful reference. No filler sentences.

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?

For a single-parameter, read-only getter with full annotation coverage and full schema coverage, the description supplies the essential framing plus a pointer to guardrails. The one real gap is the absence of any indication of what the returned configuration includes, which matters since there is no output schema.

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 description already explains the UUID-not-NIF distinction and the 403 behavior, so the baseline is 3. The description does add the semantic link that the returned config is determined by the company's NIF, but its phrasing ('the NIF in the path') muddies rather than clarifies the parameter, since the path parameter is a UUID company identifier.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Retrieves the VeriFactu configuration of this company') and adds scope detail that the configuration is keyed by NIF rather than by company record. The counterpart beel_update_verifactu_configuration is implicitly distinguishable by the verb. It stops short of naming that sibling explicitly to route the agent.

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 'Read before calling' block implies the main use case (checking whether a NIF can issue before issuing) and points to beel://guardrails/verifactu-gates. However it never states when to call this versus beel_update_verifactu_configuration, beel_get_issuing_readiness, or beel_get_tax_configuration, all of which live in the same domain and could plausibly be reached for first.

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

Deploy Server