Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_create_claim_token

Idempotent

Creates a single-use claim token and claim URL so an account holder can set a password and take ownership; issue one per account, with optional email for new holders.

Instructions

Issues a single-use claim_token, and the claim_url built from it, so the account's holder can set a password and take ownership.

  • email: send it when the account has no holder yet — the person is created by this call. Omit the body to re-issue the token for the holder the account already has. An email that differs from the existing holder's is rejected rather than replacing them.

  • Lifetime: tokens last 30 days, and only the last one issued is live. Issuing again invalidates the previous token, so the old link stops working the moment you ask for a new one.

  • Not an invitation: this hands the account itself over to its holder. To add a further person to an account that already has one, invite them with POST /v1/accounts/{account_id}/invitations.

  • Entitlement: requires manage_accounts.

Endpoint: POST /v1/accounts/{account_id}/claim-tokens

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNo
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.
idempotency_keyNoOptional idempotency key for this operation. Omit it and one is derived from the request itself, which makes a blind retry safe but also collapses a SECOND, deliberately identical operation into the first for 24 hours. Set it — to an order id, or anything unique per intended operation — whenever you mean to create something that may look identical to what you just created.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • changedInput schema / $defs / Language / description
      Previous value: -"Supported languages"New value: +"Supported languages: `es` Spanish, `en` English, `ca` Catalan.\n"
    • 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. Changed3 schema fields changedv0.5.0
    • addedInput schema / $defs / CreateClaimTokenRequest / additionalProperties
      Added value: +false
    • removedInput schema / $defs / Language / example
      Removed value: -"es"
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv0.3.1

TDQS

A4.4/5.0
Behavior4/5

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

Adds rich behavior beyond the annotations: 30-day lifetime, only the last token live, and that re-issuing invalidates the prior token so the old link dies. It also discloses the `manage_accounts` entitlement requirement. Annotations already establish idempotentHint=true and readOnlyHint=false, so the added context — particularly token invalidation and auth needs — is genuinely valuable, though return shape is left implicit.

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?

Front-loaded with the core action, then bulleted constraints (email, lifetime, not-an-invitation, entitlement) and the endpoint. Every bullet earns its place; nothing is redundant boilerplate.

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 3-parameter mutation tool with no output schema, the description covers purpose, mutation semantics, token lifecycle, auth requirement, and the alternative flow. The only gap is the undocumented `language` parameter, which is minor given the schema carries it.

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 67%, and the description reinforces the `email` semantics (required when holderless, mismatch rejection). However, it never mentions the `language` parameter at all, leaving that field to the schema. Baseline 3 fits since the description adds partial value but does not fully compensate for the uncovered parameter.

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?

States a precise verb+resource (issues a single-use claim_token and claim_url) plus the downstream effect (holder sets a password and takes ownership). It also explicitly distinguishes itself from the invitation flow, naming the sibling tool beel_create_invitation's underlying endpoint, so an agent can separate the two without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when/when-not rules: send `email` when the account has no holder, omit the body to re-issue for the existing holder, and use the invitations endpoint instead when adding a second person. The mismatch-rejection rule (a differing email is rejected, not a replacement) is stated outright.

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