Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es

beel_create_customer

Create a customer under your company NIF with Spanish tax ID validation and idempotency to prevent duplicate entries.

Instructions

Creates a new customer under this company (NIF). An Idempotency-Key identifies the same operation on the deprecated flat route, so a retry that switches route replays instead of creating twice.

Endpoint: POST /v1/companies/{company_id}/customers

⚠️ Fiscal guardrails — read before calling:

  • Why a name that does not match the census makes an invoice unsubmittable. (resource: beel://guardrails/nif-validation)

For the exhaustive rules and worked examples, call beel_docs_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
company_idYesNIF (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.
idempotency_keyNoOptional idempotency key for this operation. Omit it and one is derived from the request itself, which makes a blind retry safe but also collapses a SECOND, deliberately identical operation into the first for 24 hours. Set it — to an order id, or anything unique per intended operation — whenever you mean to create something that may look identical to what you just created.
Behavior4/5

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

The description discloses idempotency behavior (retry on deprecated flat route replays) and fiscal guardrails (name mismatch affects invoice submittability), which are not present in annotations. This adds value beyond the basic read/write flags, even though details like error responses are omitted.

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 description is concise, with the core purpose in the first sentence, followed by a warning and a pointer to docs. No redundant information; the structure is efficient and front-loaded.

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?

The tool has a complex request schema with many nested objects. The description provides high-level context and warns about fiscal issues, but does not list required fields or defaults. It references beel_docs_search for exhaustive rules, acknowledging incompleteness. Given the schema's richness, this is adequate, though not fully comprehensive.

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 description does not explain any parameters directly; it only mentions Idempotency-Key in a behavioral context. The schema provides descriptions for many fields (67% coverage), but the description does not compensate for the missing 33% or add nuance to the existing ones, so it stays at the baseline for high coverage.

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 states 'Creates a new customer under this company (NIF)' which is a specific verb-resource pair and clarifies the scope (company). It also includes the endpoint. This distinguishes it from bulk creation (beel_create_customers_bulk) and other customer operations, making the purpose unmistakable.

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

Usage Guidelines2/5

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

The description does not mention when to use this tool versus alternatives. It does not say to use for single customer creation or to use bulk for multiple, nor does it contrast with patch or delete operations. The only guidance is a pointer to docs for exhaustive rules, but no explicit selection criteria.

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