Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_list_member_grants

Read-onlyIdempotent

Lists the companies (NIFs) granted to a member and each access level, using pagination to review per-member permissions. Owners and admins return empty.

Instructions

Lists the companies (NIFs) granted to a MEMBER and the access_level of each. Empty for OWNER and ADMIN, who reach every company of the account implicitly and hold no grants.

Paginated with the usual page/limit, and the usual defaults: without them you get the first 20 grants, not all of them. Read data.pagination to walk the rest.

BeeL API endpoint: GET /v1/accounts/{account_id}/members/{member_id}/grants (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>"
    },
    "name": "beel_list_member_grants"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. The response echoes it back as `pagination.current_page`.
limitNoHow many items to return per page. The response echoes it back as `pagination.items_per_page`.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 20,
      +  "description": "How many items to return per page. The response echoes it back as `pagination.items_per_page`.",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / page
      Added value: +{
      +  "default": 1,
      +  "description": "Page number, starting at 1. The response echoes it back as `pagination.current_page`.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. First observedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the description's job is to add context — and it does: default page size of 20, the need to walk data.pagination, and the role-dependent empty result. It does not mention permission/403 behavior for this endpoint (that lives only in the account_id schema), so it is not fully exhaustive.

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?

Front-loaded with the core purpose, then role semantics, then pagination, then the endpoint reference — a sensible ordering with no filler. The pagination sentence is slightly redundant ('the usual page/limit, and the usual defaults') where one clause would do.

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 return-shape burden and does it reasonably: it names the item content (NIF + access_level) and the data.pagination envelope for walking pages. The role-dependent empty case is covered; what is missing is only minor detail such as ordering of results.

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%, so the baseline is 3. The description restates the page/limit defaults that the schema already declares (default 20, max 100) and adds the practical consequence that an unpaginated call truncates results, but it says nothing extra about account_id or member_id beyond the schema.

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 ('Lists the companies (NIFs) granted to a MEMBER') plus the returned field ('access_level'), which distinguishes it from sibling list tools such as beel_list_companies and beel_list_members. The role-scoping note ('Empty for OWNER and ADMIN') further pins down exactly what this tool covers.

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?

Gives a clear when-not signal: the call is pointless for OWNER/ADMIN because they hold no grants. It also warns that omitting page/limit yields only the first 20 results, which tells the agent when it must paginate. It stops short of naming the write-side siblings (beel_put_member_grant / beel_delete_member_grant) that an agent might otherwise reach for.

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