Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_download_representation_document

Read-onlyIdempotent

Get a presigned 5-minute download URL for a company's representation PDF, returning the generated copy until the signed one is submitted. Fails with 400 if not yet generated.

Instructions

Returns a presigned URL, valid for 5 minutes, to download the representation PDF of a company.

  • Which copy: while the document is unsigned it serves the generated one; once the signed copy has been submitted it serves that.

  • Not generated yet: a company that has not generated the document is rejected with 400.

BeeL API endpoint: GET /v1/companies/{company_id}/representation/document (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_download_representation_document"
  }
}

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. Changed2 schema fields changedv0.5.0
    • 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

A3.8/5.0
Behavior4/5

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

Beyond the readOnlyHint/idempotentHint annotations, it discloses the short 5-minute URL lifetime, the copy-selection rule (generated document until a signed copy is submitted, then the signed one), and the failure mode with status code 400. That is meaningful operational context; only the exact response payload shape is left unstated.

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 return value and URL lifetime are front-loaded in one sentence, followed by two short labeled bullets for state and failure behavior, plus a one-line endpoint reference. Every element earns its place with no redundancy.

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?

There is no output schema, so the description must carry the return-value burden; it does so by naming the presigned URL and its validity window, and it covers the main error path. It stops short of describing the exact response field names, which a caller must inspect at runtime.

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% and the single company_id parameter already carries a rich description covering UUID format, 403 behavior, and the fact that account context is derived from the ID rather than the BeeL-Active-Company header. The description adds nothing further about the parameter, 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?

The first sentence states a precise verb and resource — returns a 5-minute presigned URL to download the company's representation PDF — which is clearly distinct from the other representation tools (get, generate, cancel) and from beel_get_invoice_pdf. It does not explicitly name a sibling to route against, so a 4 rather than a 5.

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?

It implies when the tool is usable by describing the two document states (unsigned vs. signed submitted) and the 400 when nothing has been generated, which effectively hints that beel_generate_representation must run first. However, it never states when to prefer this over beel_get_representation or another PDF endpoint, so guidance is inferential.

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