Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_list_invitations

Read-onlyIdempotent

List all invitations sent to join an account, including accepted, revoked, and expired ones, to track 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.

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

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`.
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

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive behavior, so the bar is lower. The description adds genuine behavioral detail: invitations of every status remain in the list, framing the result as an access-trail record rather than a current-state snapshot.

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

Conciseness5/5

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

Two purposeful sentences plus the endpoint line; the main behavior and key status nuance are front-loaded. No filler or redundant restatement of the title.

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 low-complexity read-only list, the endpoint, status semantics, and audit-trail purpose are enough to invoke correctly. There is no output schema and no return-shape description, but the parameter docs already explain pagination echo fields, so the remaining gap is minor.

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% and already documents account_id, page, and limit, including pagination echo semantics. The description only restates account_id via the endpoint path, so it adds no meaning beyond the schema.

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 verb 'Lists' plus the resource 'invitations sent to join the account' names the operation precisely, and 'whatever their status' defines the full scope. The audit-trail sentence differentiates it from single-invitation or invitation-management siblings such as beel_get_invitation, beel_create_invitation, and beel_delete_invitation.

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 conveys clear selection context: use it to see all invitations, including revoked/expired ones, for an account. It does not explicitly name alternatives or state when not to use it, but the list-vs-single distinction is readily inferable from the sibling set.

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