Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_download_representation_document

Read-onlyIdempotent

Get a temporary presigned URL to download a company's representation PDF. The link is valid for 5 minutes and serves the generated or signed copy once submitted.

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.

Endpoint: GET /v1/companies/{company_id}/representation/document

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.

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

A4.1/5.0
Behavior5/5

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

The description adds valuable behavioral context beyond the annotations: the presigned URL is valid for 5 minutes, the served copy depends on whether a signed copy has been submitted, and ungenerated documents are rejected. Nothing contradicts the read-only, idempotent, non-destructive 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?

The description opens with the core return value, uses a short bullet list for nuanced behavior, and closes with the endpoint. Every line contributes useful information with no filler.

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?

Given a single parameter, rich parameter schema, and no output schema, the description covers the return type, URL validity, state-dependent behavior, and the key error case. An agent has enough to call the tool correctly and interpret the common failure mode.

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 company_id description already explains UUID semantics, that it is not a NIF, that the header plays no part, and the 403 behavior. The tool description adds no parameter-level detail and does not need to, since the schema already carries that weight.

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 description clearly states the action ('Returns a presigned URL... to download the representation PDF') and the resource, with a precise endpoint. It differentiates through 'presigned URL' but does not explicitly contrast with siblings like beel_get_representation or beel_generate_representation.

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 provides clear operational context, such as which copy is served and the 400 error when the document is not generated, so an agent understands when the call is valid. However, it does not name alternatives or state when to prefer a different sibling tool, leaving route selection mostly to inference.

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