Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_list_stats

Read-onlyIdempotent

Retrieve per-company invoice counts and last issuance dates for an account, with pagination and search to align results with the companies list.

Instructions

Returns, for each company of the account, how many fiscal documents it has issued and when it last issued one. What counts is described on invoice_count and last_invoice_at in the response.

Paginated with the usual page/limit, and the usual defaults: without them you get the stats of the first 20 companies, not of all of them. One row per company, over the same universe and in the same order as GET /v1/accounts/{account_id}/companies — search included — so asking both with the same page, limit and search lines the two responses up company by company.

BeeL API endpoint: GET /v1/accounts/{account_id}/companies/stats (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": {
      "account_id": "<account_id>"
    },
    "name": "beel_list_stats"
  }
}

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 — the same filter, over the same universe, as the one `GET /v1/accounts/{account_id}/companies` applies. Blank or omitted returns all.
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. Changed4 schema fields changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 20,
      +  "description": "How many items to return per page. The response echoes it back as `pagination.items_per_page`.",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / page
      Added value: +{
      +  "default": 1,
      +  "description": "Page number, starting at 1. The response echoes it back as `pagination.current_page`.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / search
      Added value: +{
      +  "description": "Case-insensitive filter on NIF, legal name or trade name — the same filter, over the same universe, as the one `GET /v1/accounts/{account_id}/companies` applies. Blank or omitted returns all.",
      +  "type": "string"
      +}
  2. First observedv0.3.1

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real behavior beyond them — the default page size silently truncates to 20 companies, and the result set mirrors the companies endpoint's universe and ordering including the search filter. It stops short of saying what counts as an 'issued' fiscal document, deferring to response fields that no output schema documents.

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 purpose is front-loaded in the first sentence and the pagination constraint is bolded and placed early. A few clauses (the endpoint URL plus docs reference, the response-field pointer) add length, but each carries operational information rather than filler.

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 four parameters and no output schema, the description covers the essential pieces: the shape of a row (one per company), the two metrics named, pagination echo behavior implied, and the ordering guarantee. The only notable gap is the definition of what is counted as an issued document, which it hands off to response fields that are not documented anywhere in this definition.

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 the baseline is 3. The description reinforces meaning by spelling out the consequence of omitting page/limit ('the stats of the first 20 companies, not of all of them') and that the search filter matches the companies endpoint, which is useful but largely restates the schema defaults.

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 description names a specific verb and resource ('Returns, for each company of the account, how many fiscal documents it has issued and when it last issued one') and scopes it to the account level. It also distinguishes itself from the plain company listing by referencing the parallel endpoint GET /v1/accounts/{account_id}/companies, so an agent can separate it from beel_list_companies without opening a 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 gives concrete operating guidance: pagination is required to see beyond the first 20 companies, and using the same page/limit/search as the companies listing lines the two responses up row by row. That is a clear usage context, though it does not explicitly state when to prefer beel_get_recurring_invoice_stats or when stats are the wrong tool.

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