Skip to main content
Glama
Sign In
sprrint

sprrint

by ejasmuhamed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sprrint_projects_add_member

Add a workspace member to a project by username or ID, assigning them the role of member or owner.

Instructions

Add a workspace member to a project. user is a username or id. role is member|owner.

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": {
      "project": "<project>",
      "user": "<user>"
    },
    "name": "sprrint_projects_add_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNomember
userYes
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 burden. It only reveals that a member is added; it does not disclose idempotency, duplicate handling, permission requirements, or side effects on existing project memberships. For a mutating tool, this is a significant transparency gap.

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 sentences with no filler. The action is front-loaded, and each clause adds either the core purpose or essential parameter meaning.

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 three-parameter mutation, the description covers the main action and most parameter meaning, but it omits project semantics, behavioral outcomes, and return behavior. It is adequate for straightforward invocation but incomplete for edge cases or authorization-aware agents.

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 0%, but the description compensates partially by explaining user ('username or id') and role ('member|owner'). However, the project parameter is left unspecified, and the default behavior of role is only available in the schema. This is partial compensation, not full.

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 states a specific verb, resource, and membership relation: 'Add a workspace member to a project.' It also clarifies that user is a username or id and role is member|owner, making the action unambiguous and distinguishing it from sibling tools like remove_member and workspace_set_role.

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 intended use is implied by the action phrase, but the description does not explicitly say when to use this tool over related siblings such as sprrint_projects_remove_member or sprrint_workspace_set_role. It provides a clear context but no 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.

Deploy Server

Other Tools