Skip to main content
Glama
Sign In
BeeL MCP server

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_get_account

Read-onlyIdempotent

Retrieve one account you provisioned by UUID to check its lifecycle status, your access level, claim-link state, and company ID when it belongs to exactly one company.

Instructions

Returns one account you provisioned, with the same shape the list returns: its lifecycle status, the access_level you hold, the state of its claim link and its company_id when the account holds exactly one company.

BeeL API endpoint: GET /v1/accounts/{account_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>"
    },
    "name": "beel_get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesIdentifier (UUID) of an account you provisioned. An account you did not provision answers exactly like one that does not exist, so its existence is never disclosed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • addedInput schema / properties / account_id / description
      Added value: +"Identifier (UUID) of an account you provisioned. An account you did not provision answers exactly like one that does not exist, so its existence is never disclosed."
  2. Changed1 schema field changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv0.3.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value by enumerating the returned fields (lifecycle status, access_level, claim-link state) and flags a conditional behavior: company_id appears only when the account holds exactly one company. It stops short of describing pagination/error responses, which matters less for a single-record read.

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 compact blocks: the return-shape sentence first, then the endpoint reference for traceability. Every phrase carries information (scope, fields, conditional logic), and nothing is redundant with the annotations.

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 no output schema, the description carries the burden of describing the response shape, and it does so at a useful level of specificity including the conditional company_id. Minor gaps remain around error/not-found signaling, but the schema covers the key disclosure caveat.

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% and the single parameter is fully documented in the schema, including the important detail that non-provisioned accounts answer identically to nonexistent ones. The description adds no meaning beyond that, so the baseline of 3 applies.

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 ('Returns one account you provisioned') and scopes it as a single-record fetch, implicitly contrasting with beel_list_accounts via 'the same shape the list returns'. It does not name the list sibling outright, so differentiation is clear but not explicit.

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?

Usage is only implied: fetch one provisioned account by its UUID. There is no guidance on when to prefer this over beel_list_accounts, how to obtain the account_id, or how to handle the not-found/non-provisioned case beyond what the schema already says.

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