Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_delete_customer

DestructiveIdempotent

Remove customers with no invoices from API access: deletion returns 404 and frees their identifier. Customers with invoices cannot be deleted; update them to inactive instead.

Instructions

Deletes a customer of this company that has no invoices.

  • What deleting means: the customer is retained internally for tax record-keeping purposes, but is no longer exposed by the API: subsequent requests to it return 404, and it is never included in the customer list, under any value of the active filter.

  • Identifier released: its NIF or alternative identifier is freed, so a new customer may be created with the same identifier.

  • Customers with invoices: they cannot be deleted and the request answers 409 CLIENT_HAS_INVOICES. To stop using a customer, update it with active set to false instead of deleting it.

Endpoint: DELETE /v1/companies/{company_id}/customers/{customer_id}

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.
customer_idYesCustomer ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • removedInput schema / $defs / UUID / example
      Removed value: -"550e8400-e29b-41d4-a716-446655440000"
    • 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.7/5.0
Behavior5/5

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

Beyond the annotations' destructiveHint=true and idempotentHint=true, the description discloses the underlying soft-delete semantics: the customer is retained internally, hidden from all API responses including active-filter results, and returns 404 on subsequent requests. It also documents the 409 CLIENT_HAS_INVOICES failure mode and identifier release, providing significant behavioral context that annotations alone cannot convey.

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 efficiently structured with a front-loaded one-sentence purpose followed by focused bullet points. Every section adds distinct value — semantics, identifier behavior, failure mode, and alternative — with no wasted words or repetition of schema content.

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?

For a destructive single-customer operation, the description covers the deletion semantics, post-deletion visibility, identifier release, conflict behavior, and the recommended non-destructive alternative. Combined with the fully described input schema and the endpoint line, this gives an agent everything needed to decide whether and how to invoke the tool correctly.

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 description coverage is 100%, so the schema already documents both parameters, including a rich explanation of company_id. The description adds behavioral context about identifiers being released but does not meaningfully extend the semantic meaning of the individual parameters beyond what the schema already provides.

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: 'Deletes a customer of this company that has no invoices.' It clearly scopes the operation to a single customer and adds the no-invoices precondition, making the tool's purpose unambiguous and distinguishable from related siblings like beel_delete_customers_bulk and beel_patch_customer.

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

Usage Guidelines5/5

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

The description explicitly explains when deletion is not allowed (customers with invoices) and directs the agent to the correct alternative: 'update it with `active` set to `false` instead of deleting it.' It also states the exact condition for using this tool — a customer with no invoices — giving clear when-to-use guidance.

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