Skip to main content
Glama

Change member role

share_role

Change the role of a member of an artifact you own, by email (owner only). Call this only when the user asks to change someone's access. role is view, comment or edit. Fails with not_found for the owner's own email or an email that is not a member. Returns { id, email, role }.

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": {
      "id": "<id>",
      "email": "<email>",
      "role": "<role>"
    },
    "name": "share_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
roleYes
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description goes beyond that by disclosing the owner-only authorization requirement, the not_found failure condition, and the exact return shape { id, email, role }. It omits whether the change notifies the member or affects existing access mid-session, so it is strong but not exhaustive.

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?

Four short sentences, front-loaded with the action and scope, then the trigger, the enum values, the failure mode, and the return shape. No redundant wording given the absence of an output schema.

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?

For a 3-required-param mutation with no output schema and no annotation detail, the description covers authorization, failure behavior, and return values. The only material gap is the unstated identity of the id parameter and any side effects on the affected member.

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 coverage is 0%, so the description must carry the load: it clarifies that email identifies the target member and enumerates the role values. However, it never states explicitly that id is the artifact identifier (only implied by 'artifact you own') and adds no format guidance for either string parameter.

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 (change the role of a member of an artifact you own) plus the lookup key (by email) and the permission scope (owner only). An agent can tell this apart from invite/link/remove operations without opening the 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?

Gives an explicit positive trigger ('Call this only when the user asks to change someone's access') and negative conditions (fails for the owner's own email or a non-member email). It does not name siblings such as share_remove or share_invite as alternatives, so routing between share tools is left partly to inference.

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