Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_get_member

Read-onlyIdempotent

Retrieves a specific account member by UUID, returning the same member data shape as the member list for direct lookup and detail display.

Instructions

Returns one member of the account, with the same shape the list returns.

BeeL API endpoint: GET /v1/accounts/{account_id}/members/{member_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>"
    },
    "name": "beel_get_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. Changed1 schema field changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.3.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only that the response shape matches the list endpoint plus the underlying HTTP route, and says nothing about not-found behavior or what a member record contains.

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 short sentences, front-loaded with the operation and its relationship to the list shape, with the endpoint and docs reference appended as compact provenance. Nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read with strong annotations, the description is serviceable, but with no output schema the phrase "same shape the list returns" offloads the return contract onto another tool rather than describing it, leaving a small but real gap.

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%, including notable detail on account_id and its 403 semantics, so the schema carries parameter meaning. The description adds no syntax or format detail beyond what the schema already provides, making the baseline 3 correct.

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?

"Returns one member of the account" states a specific verb and singular resource, and the added "same shape the list returns" implicitly positions it against the list-style siblings. It never names the alternative tool explicitly, so the differentiation is inferential rather than stated.

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?

Fetching a single member by ID is clearly implied by "one member" plus the required member_id, but there is no explicit when-to-use guidance, no statement of when to prefer beel_list_members instead, and no mention of beel_patch_member as the mutation counterpart.

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