upsert_org_memberAdd or update one organization member by email. Roles: owner, admin, member.
| Name | Required | Description | Default |
|---|---|---|---|
| role | Yes | Role to grant: owner, admin or member. | |
| Yes | Member email address. | ||
| orgId | Yes | Organization id (uuid). |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The destructiveHint annotation already signals mutability, and the description adds that the operation is keyed by email and limited to specific roles. However, it does not explain whether an existing member's role is replaced, merged, or created only if absent, leaving the 'update' semantics ambiguous.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no filler. The primary action and identifier key (email) are front-loaded, and the role restriction is stated compactly. Every phrase earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple 3-parameter tool with a complete schema and an output schema present, the description is mostly sufficient. The only notable gap is the precise upsert behavior (create vs. update semantics), which is not fully disclosed, but this is a minor omission given the low complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema covers all three parameters with 100% description coverage, so the description adds nothing beyond what the schema already provides. The role list is redudant with the role parameter description, and no new parameter-level context is introduced.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the operation: 'Add or update one organization member by email', identifying a specific verb and resource. It does not explicitly distinguish itself from sibling tools like upsert_project_member, but the org scoping is clear enough for basic selection.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for org-level membership management by email, but it does not state when to prefer this over alternatives like remove_org_member or upsert_project_member. There is clear context but no explicit exclusions or alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target a distinct resource and action, and the descriptions clearly explain boundaries. However, list_diagrams/list_documents and get_board/get_board_image are two pairs that both concern the same underlying resource, so an agent could initially select the wrong one without reading carefully.
Nearly all tool names are snake_case verb_noun pairs such as create_project, update_document, and unpublish_listing, which is very consistent. The exceptions are bare 'draw' and the non-pattern 'whoami', so it is not a perfect 5.
With 38 tools, the surface exceeds the 25+ threshold and spans orgs, projects, documents, board drawing, membership, and marketplace publishing. While each subdomain is individually reasonable, the aggregate is heavy and likely to overwhelm an agent; several related actions could be grouped or exposed more sparingly.
The set covers the main lifecycle: org/project/document CRUD, board rendering and editing, member management, and template publish/use/update. Minor gaps remain—there is no get_project single-resource read, and groups/links/notes are manipulated only through the generic update_board rather than dedicated tools—but these are workable.