BeeL MCP server

Official

Overview Schema Related Servers Score Discussions

beel_patch_customer

Patch a customer by updating only the fields you include, leaving all other data untouched. Send null to clear nullable fields while keeping the rest intact.

Instructions

Updates only the fields present in the body, leaving every other field of the customer as it is.

Null vs omitted: a field sent as null is cleared, which is different from omitting it (see PatchCustomerRequest).
Only update verb: this is the canonical way to edit a customer. There is no PUT of full replacement under the company, which would clear the fields you omit.

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

Input Schema

TableJSON Schema

Name	Required	Description
`body`	Yes
`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.
`customer_id`	Yes	Customer ID

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed25 schema fields changedv0.5.0Aug 30, 2026

addedInput schema / $defs / Address / additionalProperties
```
Added value: +false
```
removedInput schema / $defs / Address / properties / city / example
```
Removed value: -"Madrid"
```
removedInput schema / $defs / Address / properties / country / example
```
Removed value: -"España"
```
removedInput schema / $defs / Address / properties / country_code / example
```
Removed value: -"ES"
```
removedInput schema / $defs / Address / properties / door / example
```
Removed value: -"A"
```
removedInput schema / $defs / Address / properties / floor / example
```
Removed value: -"2º A"
```
removedInput schema / $defs / Address / properties / number / example
```
Removed value: -"123"
```
removedInput schema / $defs / Address / properties / postal_code / example
```
Removed value: -"28001"
```
removedInput schema / $defs / Address / properties / province / example
```
Removed value: -"Madrid"
```
removedInput schema / $defs / Address / properties / street / example
```
Removed value: -"Calle Mayor, 123"
```
removedInput schema / $defs / Email / example
```
Removed value: -"user@example.com"
```

removedInput schema / $defs / IBAN / example

Removed value: -"ES1234567890123456789012"

removedInput schema / $defs / NIF / example
```
Removed value: -"12345678A"
```
addedInput schema / $defs / PatchCustomerRequest / additionalProperties
```
Added value: +false
```
removedInput schema / $defs / PatchCustomerRequest / properties / phone / allOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/Phone"
-  }
-]
```

addedInput schema / $defs / PatchCustomerRequest / properties / phone / anyOf

Added value: +[
+  {
+    "allOf": [
+      {
+        "$ref": "#/$defs/Phone"
+      }
+    ],
+    "description": "Phone number. Send `null` to clear it."
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / $defs / PatchCustomerRequest / properties / phone / description
```
Removed value: -"Phone number. Send `null` to clear it."
```
addedInput schema / $defs / PaymentInfo / additionalProperties
```
Added value: +false
```
removedInput schema / $defs / PaymentInfo / properties / payment_term_days / example
```
Removed value: -30
```
removedInput schema / $defs / PaymentMethod / example
```
Removed value: -"BANK_TRANSFER"
```
removedInput schema / $defs / Phone / example
```
Removed value: -"+34 612 345 678"
```
removedInput schema / $defs / SWIFT / example
```
Removed value: -"ABCDESMMXXX"
```

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

First observedv0.3.1Aug 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only establish write/non-destructive/open-world; the description adds the critical behavioral traits: partial-touch semantics, the null-clears vs omitted-preserves distinction, and the absence of a full-replacement PUT. This materially reduces the chance of an agent accidentally wiping fields. No contradiction with annotations.

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?

Three tight sections with the highest-value semantic (partial update) front-loaded in the first sentence, followed by a scoped bullet on the null pitfall and a one-line endpoint. Every sentence earns its place; no filler.

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 complex mutation with a large request schema, the description surfaces the two riskiest facts an agent needs (null clearing behavior and the lack of a destructive PUT) and gives the exact endpoint. The return value is not described, but with no output schema the description delegates field-level and validation rules to the schema, which covers them.

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?

With 67% schema coverage and a schema whose PatchCustomerRequest already documents null behavior, mutual exclusivity of nif/alternative_id, and whole-replacement semantics per field, the description need not repeat field details. It adds the body-level null-vs-omitted rule and the endpoint path, but leaves most parameter-level meaning to the schema. Moderate added value over the structured data.

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 first sentence states a specific verb ('Updates'), resource ('the customer'), and the defining scope ('only the fields present in the body, leaving every other field... as it is'). The 'Only update verb' bullet further anchors it as the canonical edit operation, and the explicit PATCH endpoint unambiguously separates it from create/get/delete customer siblings.

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?

'This is the canonical way to edit a customer' is an explicit when-to-use statement, and 'There is no PUT of full replacement under the company' tells the agent not to hunt for a replacement alternative. It does not explicitly contrast with beel_create_customer for brand-new customers, but edit-vs-create is strongly implied by the partial-update framing.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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