Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_delete_company_logo

DestructiveIdempotent

Removes a company's logo from its BeeL profile; invoices generated afterward have no logo, while previously issued documents remain unchanged.

Instructions

Removes the logo of a company. Invoices rendered afterwards carry no logo, and already issued documents are unchanged. Deleting an absent logo also returns 204.

BeeL API endpoint: DELETE /v1/companies/{company_id}/logo (reference: https://docs.beel.es)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_id": "<company_id>"
    },
    "name": "beel_delete_company_logo"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is covered. The description still adds real value: it names the downstream consequence (future invoices render without a logo), confirms existing documents are untouched, and substantiates idempotency by stating a delete of an absent logo returns 204.

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 sentences: purpose first, then side effects, then the idempotency edge case, followed by a one-line endpoint/reference pointer. Nothing is redundant and the most decision-relevant facts are 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?

For a single-parameter destructive delete with rich annotations and a fully documented schema, the description covers the blast radius and the no-op case, which is what an agent needs. The only gap is that error/response behavior beyond 204 is left entirely to the schema, so it stops short of 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?

Schema coverage is 100% and the single company_id parameter is documented in exceptional detail, including UUID format, context derivation, and the 403 non-disclosure behavior. The description adds no parameter meaning of its own, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Removes the logo of a company" is a specific verb+resource and the follow-on sentence scopes the effect to future invoice rendering. No sibling in the provided list handles logos, so differentiation is implicit rather than stated, which keeps it just below the top band.

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

Usage Guidelines3/5

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

Usage is implied by the narrow, self-evident purpose, and the description does clarify the temporal scope (afterwards vs. already-issued). However, it never states when to use this versus updating the company via beel_patch_company, nor any prerequisites such as permissions or confirming the logo exists.

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