Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_put_member_grant

DestructiveIdempotent

Grant a MEMBER VIEW or OPERATE access to one company, or change an existing grant's access level while leaving the member's other grants unchanged.

Instructions

Grants a MEMBER access to one company, or changes the access_level of an existing grant. Only the company in the path is touched.

  • Scope: the member's other grants are left exactly as they were.

  • access_level: VIEW or OPERATE. NONE is not accepted here — remove access by deleting the grant.

  • Eligible members: grants apply only to MEMBER. OWNER and ADMIN reach every company implicitly and cannot receive grants.

BeeL API endpoint: PUT /v1/accounts/{account_id}/members/{member_id}/grants/{company_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>",
      "member_id": "<member_id>",
      "company_id": "<company_id>",
      "body": "<body>"
    },
    "name": "beel_put_member_grant"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
member_idYesMembership unique UUID.
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.
company_idYesUnique identifier (UUID) of the company within the account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.0
    • addedInput schema / properties / body / type
      Added value: +"object"
  2. Changed3 schema fields changedv0.5.0
    • addedInput schema / $defs / PutMemberGrantRequest / additionalProperties
      Added value: +false
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / company_id / description
      Previous value: -"Company (NIF) unique UUID within the account."New value: +"Unique identifier (UUID) of the company within the account."
  3. First observedv0.3.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true and readOnly=false, so the description needs less. It still adds useful behavioral context the annotations lack: only the path company's grant changes and the member's other grants are untouched, plus the eligibility and `NONE` rejection rules. It does not discuss effects of overwriting an existing `access_level`, which is the one remaining gap.

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 main sentence, then three short labeled bullets covering scope, access-level constraint and eligibility. No filler, and the endpoint reference is a compact trailing line.

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?

No output schema exists, and the description gives enough for correct invocation on a mutating grant endpoint: scope isolation, allowed values, and member-type eligibility, with auth failure semantics already in the schema. It stops short of saying what a successful response contains or how repeated PUTs behave, minor for a tool with strong annotations.

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?

Schema coverage is 75%, so the schema already documents most parameters. The description adds meaning beyond it by explaining that the company comes from the path rather than the body and by clarifying why only `VIEW`/`OPERATE` appear in the enum (`NONE` must be done by deletion).

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 specific verb and resource ('Grants a `MEMBER` access to one company, or changes the `access_level` of an existing grant') and scopes it to the single company in the path. This clearly separates it from `beel_delete_member_grant` and `beel_list_member_grants`.

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?

Explicitly says when to use and when not to: `NONE` is rejected and removal must go through deleting the grant, naming the alternative tool's behavior. It also states the eligible-member rule (only `MEMBER`; `OWNER`/`ADMIN` cannot receive grants), which prevents misuse.

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