dolphin-anty-mcp

Create a team member

create_team_user

Add a new user to your Dolphin{anty} team, specifying role, permissions, and profile limits. Requires admin access.

Instructions

Add a member to the team. Only admins can do this.

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": {
      "username": "<username>",
      "password": "<password>",
      "role": "<role>"
    },
    "name": "create_team_user"
  }
}

Input Schema

Name	Required	Description
`role`	Yes
`bpLimit`	No	Profile cap; ignored if unlimitedBp.
`password`	Yes
`username`	Yes	Login email; must be unique across Dolphin{anty}.
`teamleads`	No	Supervising team-lead ids. Only valid when `role` is 'user'.
`canCreateBp`	No	Allow creating browser profiles.
`displayName`	No
`unlimitedBp`	No	Lift the profile cap. Must be sent together with canCreateBp=true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a mutation but not destructive. The description adds the admin-only permission requirement, which is useful context beyond annotations. However, it doesn't disclose other behavioral traits like return values or side effects.

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 fluff. 'Only admins can do this' earns its place as a key permission constraint, making it appropriately front-loaded and concise.

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?

For a create operation with 8 parameters and no output schema, the description is too sparse. It doesn't mention required fields, the role enum, or any expected response. The admin restriction helps but leaves many operational gaps that the moderate schema coverage cannot fully bridge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 63%, which is moderate but not high enough to rely on entirely. The tool description provides no parameter semantics whatsoever, leaving the undocumented parameters (role, password, displayName) without additional clarity. The description adds no value over the schema.

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 clearly states 'Add a member to the team' – a specific verb and resource. It implies creation and differentiates from update/delete/list by the action word 'Add', but it doesn't explicitly name sibling alternatives or contrast with them, so it falls short of a 5.

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?

No guidance is provided on when to use this tool versus alternatives like update_team_user or delete_team_user. The only additional context is 'Only admins can do this,' which is an authorization constraint, not a usage guideline.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server