Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_list_companies

Read-onlyIdempotent

Lists the companies (NIFs) belonging to an account, with the primary company first. Supports case-insensitive search, pagination, and optional issuing-readiness data.

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.

BeeL API endpoint: GET /v1/accounts/{account_id}/companies (reference: https://docs.beel.es)

⚠️ Read before calling:

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

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": {
      "account_id": "<account_id>"
    },
    "name": "beel_list_companies"
  }
}

Input 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. Changed1 schema field changedv0.10.0
    • addedInput schema / properties / include / type
      Added value: +"string"
  2. Changed2 schema fields changedv0.5.0
    • removedInput schema / $defs / CompanyInclude / example
      Removed value: -"readiness"
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv0.3.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real behavior: result ordering, empty-list-instead-of-error semantics, and the fact that `pagination` is always present even for a one-item page. The unexpanded guardrail pointer (`beel://guardrails/multi-nif`) signals a multi-NIF selection rule without stating it, which is the only real gap.

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?

Bulleted structure is front-loaded with the core behavior and the pagination warning sits near the top, so the highest-risk detail is not buried. A couple of bullets duplicate schema text (search fields, include=readiness), which is minor waste but not harmful.

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 carries the return-shape burden and does explain the item concept (companies/NIFs), ordering, the empty-list case, and the always-present pagination block. It does not enumerate other per-company fields, but it points to the API reference, which is reasonable for a list endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema: the warning that omitting `page`/`limit` silently truncates to 20 items, and that `pagination` is echoed in every response. The `search` and `include` bullets largely restate the schema descriptions.

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 gives a specific verb and resource ('Returns the companies (NIFs)') plus ordering semantics (primary company first), and the 'Series' bullet explicitly rules out a sibling resource and points to where series live instead. An agent can distinguish this from beel_list_accounts and beel_list_series without opening any schema.

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?

It states when to add `include=readiness`, warns that without `page`/`limit` you get only the first 20 items, and excludes series to a different endpoint. It stops short of naming a competing sibling tool for fetching a single company (e.g. beel_get_company), so the alternative routing is implied rather than complete.

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