Skip to main content
Glama
Sign In
sprrint

sprrint

by ejasmuhamed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sprrint_workspace_set_role

Change a workspace member's role to owner, admin, or member by providing the user ID.

Instructions

Change a workspace member role. role is owner|admin|member.

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": {
      "user_id": "<user_id>",
      "role": "<role>"
    },
    "name": "sprrint_workspace_set_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. 'Change' indicates mutation, but the description omits permissions required, constraints on role transitions, and potential effects such as changing an owner. For a mutation tool, this leaves important behavior undocumented.

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?

The description is two short, front-loaded sentences. The core action comes first, and the role value domain is stated without any filler. Every word contributes.

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 simple two-parameter mutation with no annotations and no output schema, the description gives enough to attempt a basic call: the purpose and valid role values. However, it omits preconditions, permission context, and role-transition caveats, making it adequate but incomplete.

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?

The schema has 0% description coverage and no enum on the role parameter. The description adds meaningful value by stating 'role is owner|admin|member', but it does not explain user_id beyond what the parameter name implies. Compensation for the missing schema descriptions is only partial.

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?

The description uses a specific verb ('Change') and resource ('workspace member role'), and it clarifies the role domain with 'owner|admin|member'. It is not a tautology, but it does not explicitly distinguish itself from siblings like sprrint_workspace_update, sprrint_workspace_invite, or sprrint_workspace_remove_member.

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?

The description implies when to use the tool: when a workspace member's role needs to change. However, it provides no explicit guidance on when not to use it or which sibling tool to prefer, so the usage decision is left mostly to inference.

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