Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_list_companies

Read-onlyIdempotent

Lists companies (NIFs) for an account, primary company first. Supports case-insensitive search by NIF, legal name, or trade name and returns an empty list when no companies exist.

Instructions

Returns the companies (NIFs) belonging to the account in the path, ordered with the primary company first. An account with no companies yet returns an empty list rather than an error.

  • search: filters case-insensitively on NIF, legal name and trade name.

  • include=readiness: adds each company's issuing-readiness block.

  • pagination: present only when the request is paginated — that is, when any of page, limit or search is sent. It is omitted for the full list.

  • Series: not part of this response. Read them from GET /v1/companies/{company_id}/series.

Endpoint: GET /v1/accounts/{account_id}/companies

⚠️ Fiscal guardrails — read before calling:

  • Which company an operation acts on, and how that is selected. (resource: beel://guardrails/multi-nif)

For the exhaustive rules and worked examples, call beel_docs_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, starting at 1. The response echoes it back as `pagination.current_page`.
limitNoHow many items to return per page. The response echoes it back as `pagination.items_per_page`.
searchNoCase-insensitive filter on NIF, legal name or trade name. Blank/omitted returns all.
includeNoInclude derived data. `readiness` adds each company's issuing-readiness status.
account_idYesYour own account, or an account you provisioned. It — not the credential — decides which account the operation acts on; a `403` is returned when you do not reach it, the same response an account that does not exist gets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • removedInput schema / $defs / CompanyInclude / example
      Removed value: -"readiness"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), and openWorldHint is reflected by the series-exclusion note pointing elsewhere. The description adds genuine behavioral value beyond annotations: empty list instead of error, primary-company-first ordering, and the conditional presence of the pagination block. This aligns with and extends the annotations without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, then organized into scannable bullets for each parameter, an endpoint line, a guardrail warning, and a docs pointer. It is longer than a minimal description but every section earns its place — particularly the fiscal guardrails callout and the series-exclusion note, which prevent misuse. The structure is clean and well-ordered.

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 5-parameter list tool with no output schema and rich annotations, the description is thorough: it covers empty-list behavior, ordering, pagination presence, the series exclusion with an alternative endpoint, and a fiscal guardrail reference. The account_id subtlety is handled by the schema's detailed description, and the pointer to beel_docs_search for exhaustive rules closes remaining gaps. Minor omissions (response shape details) are acceptable given annotations carry the safety profile.

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%, so every parameter is already documented: page, limit, search, include, and the detailed account_id semantics (it, not the credential, decides the account; 403 on non-reachability). The description's per-param bullets (search filtering, include=readiness, pagination condition) largely echo the schema. It adds marginal value via the pagination presence condition, which is response-level rather than parameter-level detail. Baseline 3 is appropriate for full coverage.

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 opening sentence uses a specific verb and resource: 'Returns the companies (NIFs) belonging to the account in the path.' It distinguishes itself from related siblings by explicitly scoping to companies and stating what is NOT returned ('Series: not part of this response'), routing the agent to a separate endpoint. The primary-company ordering and empty-list-vs-error behavior add precision that clearly separates it from other list tools.

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 gives clear context: it states the empty-list behavior, the conditions under which pagination appears, and explicitly excludes series, directing the agent to GET /v1/companies/{company_id}/series as the alternative. It references a fiscal guardrail resource to read before calling and points to beel_docs_search for exhaustive rules. It lacks an explicit 'use this instead of X' sibling comparison, but the boundaries are well delineated.

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