Skip to main content
Glama
Sign In
dVersum MCP Server

dVersum MCP Server

Official
by dversum
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

add_project_member

Add a user to a project using their user UUID and the project UUID, granting them access to collaborate on tasks and deliverables.

Instructions

Add a member to a project.

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_id": "<project_id>",
      "user_id": "<user_id>"
    },
    "name": "add_project_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesThe user UUID to add
project_idYesThe project UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It fails to mention permissions required, behavior if the user is already a member, or any side effects. The only disclosed behavior is the add operation itself.

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 a single, concise sentence that communicates the core purpose without any fluff. It is front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a mutation with no annotations and no output schema, so the description must compensate. It is too terse, lacking details about prerequisites, error cases, or relationship to invite_member. Users are left guessing about edge cases and required permissions.

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 input schema fully documents both parameters (user_id and project_id) with descriptions, so the baseline is 3. The description adds no extra meaning beyond the schema, but the schema alone is sufficient for parameter understanding.

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 'Add a member to a project' uses a specific verb and resource, clearly stating the action. It distinguishes itself from sibling tools like remove_project_member and list_project_members, and the name reinforces the purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no context on when to use this tool versus alternatives such as invite_member (which likely adds organization members) or update_project for changing membership. No exclusions or prerequisites are mentioned.

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