Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_get_usage

Read-onlyIdempotent

Retrieve provisioned account counts and billable usage for your account to support offline B2B invoicing.

Instructions

Returns how many accounts you have provisioned and the billable count that follows from them — the figure behind your offline B2B invoice.

  • Billable unit: the provisioned account, not the real NIF. Every account you provision counts as one, empty and unclaimed ones included.

  • account_id: your own account. Usage is a property of the provisioner, not of each provisioned account, so any other id returns 404.

  • Entitlement: requires manage_accounts.

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

Input Schema

NameRequiredDescriptionDefault
account_idYesYour own account id.

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

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

Annotations already declare this read-only, idempotent and non-destructive, so the bar is lower, yet the description still adds substantial behavior: the billable unit is the provisioned account rather than the real NIF, empty and unclaimed accounts count too, and a foreign account_id yields 404. It also discloses the manage_accounts entitlement requirement. That is the kind of counting-rule and failure-mode detail an agent cannot get from structured fields.

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 lead sentence front-loads what is returned, and the bullets each carry distinct information (billable unit, id semantics, entitlement). The closing API-endpoint and docs-reference line is conventional boilerplate, and the invoice framing clause is slightly ornamental, keeping it just under the top mark.

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?

There is no output schema, so the description correctly carries the return-value burden by naming the two figures produced. It also covers entitlement, the counting rule, and the 404 case. What it does not state is the response shape or field names for those two numbers, a small gap for a tool whose only output is a count pair.

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 the schema already says account_id is 'your own account id', so the baseline is 3. The description goes beyond it by explaining why: usage is a property of the provisioner, not of each provisioned account, which is the reason other ids 404. That is genuinely useful context, so it sits at the top of the baseline band.

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?

The description states a specific verb and resource: it returns the provisioned-account count and the resulting billable count, framed as the figure behind an offline B2B invoice. That is materially more precise than a title restatement. It does not, however, explicitly distinguish itself from the nearby beel_list_accounts or beel_list_stats siblings, leaving the agent to infer that this returns aggregate counts rather than records.

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?

Usage context is clear: this is the endpoint to call when you need the billable-account figure for invoicing, and it requires the manage_accounts entitlement. The description also rules out a wrong invocation pattern by stating that any account_id other than your own returns 404. It stops short of naming an alternative tool for per-account or list-style needs, so there are no explicit exclusions beyond the id constraint.

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