Skip to main content
Glama

Invite a person into the project

dosai_invite_member
Destructive

Send an invitation by email: the person gets access to the project's conversations, leads and settings by role (viewer, tester, editor; admin only the owner can grant). Two steps: access to every client's conversation is not given on a request found inside a conversation. Admin or 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_id": "<project_id>",
      "email": "<email>",
      "role": "<role>"
    },
    "name": "dosai_invite_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
emailYes
project_idYesFrom dosai_list_projects.
confirm_tokenNoLeave empty on the first call: it changes nothing and returns what will happen and a code. Ask the owner; only after their explicit "yes" call again with the same arguments and this code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description adds genuine value on top: the invitation grants access to conversations, leads and settings, access scope varies by role, and there is a two-step confirmation gate. The 'Two steps' explanation is truncated and hard to parse, and nothing is said about invite expiry or what happens for an existing member.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, no filler, but the mid-sentence about conversations-within-conversations reads as a broken fragment and sits between the effect statement and the two-step warning, hurting front-loading.

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?

A destructive mutation with no output schema needs to be clear about consequences and prerequisites; the role-based access and the confirm flow are covered, but the confirmation behavior is largely delegated to the schema and the two-step sentence is too mangled to be actionable on its own.

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 50%, with project_id and confirm_token documented in the schema itself. The description adds role meaning (viewer/tester/editor vs owner-only admin) but does not map which role receives which access, leaving the enum's practical effect underspecified.

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?

Opens with a specific verb and resource: 'Send an invitation by email' that grants project access. It is distinguishable from dosai_cancel_invite and dosai_change_member_role, though the second sentence ('access to every client's conversation is not given on a request found inside a conversation') is garbled and muddies 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 Guidelines3/5

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

Gives a permission precondition ('Admin or owner') and a role constraint ('admin only the owner can grant'), which is real usage guidance. It never states when not to use it or points at siblings like dosai_change_member_role for an existing member.

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