Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_list_companies

Read-onlyIdempotent

List companies (NIFs) for a specified account, ordered with the primary company first. Filter by NIF, legal name, or trade name, and optionally include issuing-readiness status.

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.

  • Paginated, always: without page and limit you get the first 20 companies, not all of them, and pagination is present in every response — a single-company account simply gets a one-item page.

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

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

⚠️ Read before calling:

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

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.3/5.0
Behavior5/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description adds substantive behavior on top: pagination is always applied with a 20-item default, `pagination` is present in every response, and a company-less account returns an empty list rather than an error. It also flags a guardrails resource governing which company an operation targets.

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?

Front-loaded summary sentence followed by tight bullets for search, include, pagination and series. Slightly verbose where it repeats page/limit defaults already in the schema, but each section is scannable and earns its place.

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?

With no output schema, the description steps in to describe the response shape (ordered list, pagination envelope, empty-list case), which is what an agent needs. The multi-NIF guardrail is only pointed at rather than explained, leaving a small gap.

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%, so page, limit, search, include and account_id are all documented in the schema itself. The description largely restates the same filters, adding no syntax or format detail beyond what the schema provides; baseline 3 is appropriate.

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?

States a specific verb and resource ('Returns the companies (NIFs) belonging to the account in the path') plus ordering semantics ('primary company first') and the empty-account edge case. This clearly separates it from the single-resource sibling beel_get_company.

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?

Gives a clear boundary condition by stating series data is NOT in this response and routing the caller to a different endpoint, and documents the implicit pagination default. It never explicitly contrasts against sibling list tools like beel_list_accounts, so it stops short of full when/when-not guidance.

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