Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_get_invitation

Read-onlyIdempotent

Retrieve a specific account invitation by account and invitation ID, including its status (accepted, revoked, or expired) to audit who was granted access to fiscal data.

Instructions

Returns one invitation of the account, with the same shape the list returns. An invitation stays readable for its whole life: ACCEPTED, REVOKED and EXPIRED ones are returned with their status, because the record is the trail of who was granted access to the account's fiscal data and revoking it does not erase it.

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

Input Schema

NameRequiredDescriptionDefault
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.
invitation_idYesIdentifier (UUID) of an invitation of the account in the path, as returned when it is created or listed. An invitation of another account answers `404`, exactly like one that does not exist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • addedInput schema / properties / invitation_id / description
      Added value: +"Identifier (UUID) of an invitation of the account in the path, as returned when it is created or listed. An invitation of another account answers `404`, exactly like one that does not exist."
  2. Changed1 schema field changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv0.3.1

TDQS

A4.2/5.0
Behavior4/5

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

The description provides excellent behavioral context by explaining that the invitation record is persistent and searchable even when marked as ACCEPTED, REVOKED, or EXPIRED. This addresses the data's lifecycle beyond the API's status field.

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 description is direct, but slightly marred by the inclusion of the full API endpoint and the detailed audit trail explanation. However, the key functional characteristic is conveyed efficiently at the start.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The definition is highly complete. It covers the specific operation, the inputs required, the persistent nature of the data, and the exact API path, making it extremely robust for an agent.

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?

While the schema covers 100% of parameters, the description adds value by explaining the semantic role of 'account_id'—that it dictates the operational context and dictates specific error responses (403), which is critical semantic information.

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 purpose is stated clearly: 'Returns one invitation of the account.' This specifically targets a single resource retrieval, which distinguishes it from the list operation available via siblings like beel_list_invitations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is used when a specific invitation ID is known, but it does not explicitly state when to prefer this over related functions like listing or creating an invitation.

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