Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_list_invitations

Read-onlyIdempotent

Lists all invitations sent to join an account, including accepted, revoked, and expired ones, so you can audit who was granted access to fiscal data.

Instructions

Lists the invitations sent to join the account, whatever their status. Accepted, revoked and expired invitations stay in the list: the record is the trail of who was granted access to the account's fiscal data.

BeeL API endpoint: GET /v1/accounts/{account_id}/invitations (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_invitations"
  }
}

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`.
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.5.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.3.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine behavioral context beyond them: accepted, revoked and expired invitations are retained in the result, meaning callers get full history rather than only pending records. It does not discuss result volume or pagination defaults, which the schema covers instead.

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 core statement is front-loaded in the first sentence, with the retention rationale following and the endpoint reference last. Two sentences plus a reference line carry no real padding, though the status clause is restated twice ("whatever their status" then the enumeration).

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 simple read-only list with three fully documented parameters and no output schema, the definition covers purpose, retention semantics and endpoint identity adequately. Only the shape of returned invitation records is left unstated, which is a minor gap given no output schema exists.

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%, including detailed page/limit/account_id text, so the baseline is 3. The description adds only indirect framing ("the account's fiscal data") and no syntax or format meaning beyond the schema.

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?

States a specific verb and resource ("Lists the invitations sent to join the account") and pins down scope with "whatever their status", which separates it from any filtered view. It does not explicitly name the neighbouring tools (beel_get_invitation, beel_list_members, beel_create_invitation), so the distinction is inferable rather than stated.

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 reason to call it — reconstructing the trail of who was granted access to the account's fiscal data — and the "whatever their status" note tells the agent that filtering by status is not possible here. There is no explicit when-not or named alternative, so it stops short of full routing 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