Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es

beel_get_issuing_readiness

Read-onlyIdempotent

Check if a company (NIF) is ready to issue a standard invoice now, returning a readiness flag and listing any blockers that prevent it.

Instructions

Returns whether a company (NIF) can issue its STANDARD invoice right now in the environment of the request, and the blockers that stop it otherwise. ready is true only when blockers is empty. Readiness is a per-NIF property, evaluated independently for each company of the account.

Issuing any fiscal document requires the company to be activated in the environment of that document, whether or not it goes to VeriFactu. The VeriFactu capability chain — AEAT census and signed representation — is additionally demanded only when the company applies VeriFactu by default, the same derivation invoice creation uses when verifactu_enabled is omitted; a company with VeriFactu off is ready with a NIF, a default series and an activation. Issuing an invoice with an explicit verifactu_enabled: true still enforces the full chain at emission time regardless of this answer, and the separate verifactu block reports that chain independently of the setting.

This does not evaluate the account's quota or subscription, nor the payload of any particular invoice.

Endpoint: GET /v1/companies/{company_id}/issuing-readiness

⚠️ Fiscal guardrails — read before calling:

  • Which company an operation acts on, and how that is selected. (resource: beel://guardrails/multi-nif)

For the exhaustive rules and worked examples, call beel_docs_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesNIF (company) whose issuing readiness is evaluated. 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.
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description goes well beyond that: it defines the semantics of `ready` and `blockers`, explains the VeriFactu chain conditions, clarifies that readiness is per-NIF and independent per company, and even details behavior when `verifactu_enabled` is explicit. This adds substantial behavioral context that an agent cannot infer from annotations alone. No contradictions found.

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 structured in clear paragraphs with the primary purpose front-loaded. Every sentence earns its place: the VeriFactu explanation is critical, the explicit exclusions prevent false expectations, and the guardrails pointer is a useful reference. The length is justified by the complexity of the tool without redundancy.

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?

Given the tool's complexity and the absence of an output schema, the description provides a reasonable outline of the response semantics (ready, blockers, verifactu block) and points to beel_docs_search for full details. It lacks an exhaustive enumeration of possible blockers or the exact response shape, but the pointer to docs compensates. For a read-only check with annotations covering safety, this is sufficiently complete.

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?

The single parameter `company_id` is already fully documented in the input schema (100% coverage), including its semantics as a NIF, its role as the sole source of context, and the 403 response behavior. The tool description adds no further parameter-specific information. Per the calibration guidelines, baseline 3 is appropriate when schema coverage is high.

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 whether a company (NIF) can issue its STANDARD invoice right now' — clearly stating the action and the subject. It distinguishes this from other fiscal tools by focusing on readiness and blockers, and it clarifies the per-NIF scope. This is unambiguous and unique among the many sibling tools.

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?

The description explains when this tool is relevant (pre-check before issuing a standard invoice) and explicitly disclaims what it does not evaluate (quota, subscription, payload), which prevents misuse. It points to docs for exhaustive rules and includes a fiscal guardrails pointer. It does not explicitly name an alternative tool like beel_issue_invoice, but the context strongly implies readiness is a precursor. This is clear enough for an agent to decide when to call it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/beel-es/beel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server