Skip to main content
Glama

member

Create, invite, and manage members in project shared spaces with role assignment and ownership transfer.

Instructions

member(action) — openbox (shared space) members and permissions. An openbox is a project's shared space (invite-only, not 'public').

  • member('new', openbox=, display_name=) create an openbox (you = owner)

  • member('invite', openbox=, role=, kind=) issue an invite code (owner). kind='project' = project member

    • who= — reissue invite (targets an existing project identity, rotates the session)

  • member('join', code=, display_name=) join with an invite code (first join)

  • member('subscribe', openbox=, url=) connect an openbox you're already a member of via URL (authenticates as your identity)

  • member('list', openbox=) list members

  • member('role', openbox=, who=, role=) change a member's role (viewer↔member, owner)

  • member('transfer', openbox=, who=) transfer owner (who=member_id, double confirmation)

  • member('leave', openbox=) leave yourself (owner gets 409, transfer first) remove: rm(member='', openbox='') delete the whole openbox: rm(openbox='') — owner only, double confirmation (openbox= is an alias for name= — both work.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
whoNo
codeNo
helpNo
kindNo
nameNo
roleNo
actionNo
openboxNo
expires_hNo
display_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: owner-only operations, double confirmation for transfer, error on leave for owner (409), and side effects like session rotation on reissue.

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 description is long but well-structured with bullet points and clear sections. It could be slightly more concise, but every part adds value for the tool's complexity.

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?

Given the tool's complexity (11 parameters, multiple actions), the description covers all necessary context: openbox concept, action types, parameter usage, error conditions, and alternative tools. Output schema presumably covers return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, but the description defines all parameters via usage examples and explanations (e.g., action, openbox, role, kind, who, code, url). It fully compensates for missing schema descriptions.

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 clearly states the tool handles openbox (shared space) members and permissions, with a one-line summary and detailed action list. It distinguishes the tool's scope from siblings by explicitly mentioning removal via 'rm' tool.

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?

The description provides explicit when-to-use guidance for each action, including when to delegate to the 'rm' tool for deletion, and lists prerequisites (e.g., owner-only for invite, transfer has double confirmation).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/linklore/linklore-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server