Skip to main content
Glama

What a person can reach

access_person
Read-only

What one person reaches in the organization and why: their role (owner or member), their teams (and whether they maintain each), every wiki they hold with its level (read, write or admin), capabilities and reasons (via: org, a grant to them as user, a team, or owner), and the sites they may use or manage. Without user, the caller. Only an organization's owners may ask about someone else.

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": {
      "org": "<org>"
    },
    "name": "access_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose people, teams and access to use. Required on every call, even when only one organization is listed; a path never names it.
userNoThe person's user id, as members_list gives it (user_id). Leave out to ask about the caller.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / org / description
      Previous value: -"slug of the organization whose people, teams and access to read. Required on every call, even when only one organization is listed; a path never names it."New value: +"slug of the organization whose people, teams and access to use. Required on every call, even when only one organization is listed; a path never names it."
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely new behavior: the permission gate on querying other users, the default-to-caller behavior, and a detailed picture of the response contents including the reason/via for each capability. With no output schema present, that return-shape disclosure is doing real work.

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 purpose is front-loaded in the first clause, and the enumeration, default behavior, and permission restriction follow in a compact form. The long parenthetical list is dense but each element carries information; only the 'Without user, the caller' clause duplicates the schema and could be dropped.

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

Completeness5/5

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

For a two-parameter, read-only lookup with full schema coverage and no output schema, the definition supplies everything an agent needs: what is returned, what happens when the optional parameter is omitted, and who is allowed to make the call. Nothing material is missing for correct invocation.

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 both parameters are already documented in the schema. The description's 'Without user, the caller' restates what the schema's user description already says, and the org parameter is not discussed at all beyond being implied. It therefore adds little meaning beyond the structured fields, which is the baseline 3 case.

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?

The description names a specific resource (one person's reach in the organization) and enumerates exactly what is reported: role, team memberships and maintainer status, per-wiki access level, capabilities with the reason/via, and site permissions. That enumeration cleanly separates it from siblings like access_wiki (wiki-centric) and members_list (roster), so an agent can choose 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 Guidelines4/5

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

It states the default subject ('Without user, the caller') and an explicit authorization precondition ('Only an organization's owners may ask about someone else'), and it points to members_list as the source of a valid user_id. What it lacks is an explicit statement of when to prefer this over access_wiki or team_* lookups, so the alternative-selection guidance is implied rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources