Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_get_my_identity

Read-onlyIdempotent

Retrieve the authenticated principal's account ID, email, name, logo, language, and credential details to confirm which account a BeeL credential belongs to and whether it is valid.

Instructions

Returns the identity of the authenticated principal: the account the credential belongs to, the person's email, name, logo and interface language, and a description of the credential itself. Unlike every other operation, it requires no scope — any valid credential resolves, so a 200 confirms the credential works and tells you which account it belongs to, and a 401 that it does not.

  • account_id: identifies who the credential belongs to, not what it is currently pointed at; selecting a different company with BeeL-Active-Company does not change it.

  • name: resolves as trade_name ?? legal_name of the active fiscal profile, and is null until onboarding creates one.

  • credential: describes the credential the call was authenticated with — its type, the environment it operates on and the permissions it holds — so a client can adapt what it offers instead of discovering the limits through a 403.

  • Caching: responses are never cached (Cache-Control: no-store).

BeeL API endpoint: GET /v1/me/identity (reference: https://docs.beel.es)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "beel_get_my_identity"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses that no scope is required (any valid credential resolves), the meaning of 200 and 401 responses, that account_id is unaffected by the BeeL-Active-Company header, that name resolves as trade_name ?? legal_name and may be null pre-onboarding, and that responses are never cached. This is substantial behavioral context that the annotations alone do not convey.

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 bullets organize the field semantics cleanly. It is slightly long for a zero-parameter tool, but each bullet carries distinct, non-redundant information and the caching note is short.

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?

With no output schema, the description correctly carries the burden of explaining return values and does so field by field. Combined with the auth-failure semantics and caching behavior, an agent has everything needed to call and interpret this tool correctly.

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?

The tool has zero input parameters, so the baseline is 4 and there is nothing for the description to disambiguate on the input side. The field-level explanation of the response (account_id, name, credential) adds value, though strictly it describes output rather than parameters.

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 opens with a specific verb and resource — 'Returns the identity of the authenticated principal' — and enumerates the fields returned (email, name, logo, language, credential). It explicitly distinguishes itself from siblings by noting it is the one operation requiring no scope, so an agent can identify it without inspecting other schemas.

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 explicit when-to-use guidance: call it to confirm a credential works and to learn which account it belongs to, and it explains how to interpret 200 vs 401. It does not name a related sibling such as beel_update_me or state any exclusions, so the guidance is clear but not a full when/when-not/alternative map.

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