Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_patch_product

Partially update a product by changing only the fields you send, leaving omitted ones—such as tax rates—untouched via a PATCH request.

Instructions

Updates only the fields present in the body, leaving every other field of the product as it is — in particular main_tax, irpf_rate and equivalence_surcharge_rate.

  • Null vs omitted: a field sent as null is cleared, which is different from omitting it (see PatchProductRequest).

  • Only update verb: the total replacement PUT /v1/products/{product_id}, which reset the omitted fields to their creation defaults, is not carried over to the canonical form.

Endpoint: PATCH /v1/companies/{company_id}/products/{product_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
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.
product_idYesProduct unique UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changedv0.5.0
    • addedInput schema / $defs / PatchProductRequest / additionalProperties
      Added value: +false
    • removedInput schema / $defs / PatchProductRequest / properties / active / example
      Removed value: -true
    • removedInput schema / $defs / PatchProductRequest / properties / code / example
      Removed value: -"SERV-001"
    • removedInput schema / $defs / PatchProductRequest / properties / default_price / example
      Removed value: -85.5
    • removedInput schema / $defs / PatchProductRequest / properties / description / example
      Removed value: -"Specialized technical consulting services"
    • removedInput schema / $defs / PatchProductRequest / properties / equivalence_surcharge_rate / example
      Removed value: -5.2
    • removedInput schema / $defs / PatchProductRequest / properties / irpf_rate / example
      Removed value: -15
    • removedInput schema / $defs / PatchProductRequest / properties / name / example
      Removed value: -"Technical consulting"
    • removedInput schema / $defs / PatchProductRequest / properties / unit / example
      Removed value: -"hours"
    • removedInput schema / $defs / ProductCategory / example
      Removed value: -"CONSULTING"
    • removedInput schema / $defs / RegimeKey / example
      Removed value: -"01"
    • addedInput schema / $defs / TaxInfo / additionalProperties
      Added value: +false
    • removedInput schema / $defs / TaxInfo / example
      Removed value: -{
-  "percentage": 21,
-  "regime_key": "01",
-  "type": "IVA"
-}
    • removedInput schema / $defs / TaxInfo / properties / percentage / example
      Removed value: -21
    • removedInput schema / $defs / TaxType / example
      Removed value: -"IVA"
    • 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.2/5.0
Behavior4/5

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

The description discloses meaningful beyond-annotation behavior: null clears a field while omission keeps the current value, and it calls out that main_tax, irpf_rate, and equivalence_surcharge_rate are preserved unless explicitly sent. The annotations already mark readOnlyHint=false and openWorldHint=true, so this behavioral detail adds useful nuance rather than contradicting anything.

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 tight, front-loaded with the core semantic, and uses short bullets for the key distinctions. Every sentence contributes either a behavioral rule or a contrast with the alternative PUT operation, with 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?

The description covers the essential calling context: endpoint, partial-update semantics, null handling, and the difference from PUT replacement. The input schema provides rich per-field detail, so the missing response-shape information is not critical, but with no output schema a brief note on what the PATCH returns would make it fully 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 description reinforces the null-versus-omitted semantics that the PatchProductRequest schema also documents, but it does not add much parameter-level meaning beyond what the schema provides. With 67% schema description coverage, the schema carries most of the parameter documentation burden, and the description makes a modest supplementary contribution by highlighting the three tax-related fields.

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 precise verb and resource: 'Updates only the fields present in the body' on a product. It clearly distinguishes this PATCH from the total-replacement PUT, so an agent can tell exactly what operation this tool performs.

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 explicitly contrasts this PATCH with the 'total replacement PUT /v1/products/{product_id}' that resets omitted fields, giving clear guidance on which verb to choose. It does not explicitly state 'use this tool when you want a partial update,' but the semantics are strongly implied by the wording and the endpoint.

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