Skip to main content
Glama
Sign In
dolphin-anty-mcp

dolphin-anty-mcp

by someorgyouwontcareabout
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List team members

list_team_users
Read-only

List all members of your team account, including their roles and profile limits, to manage permissions.

Instructions

List members of the current team account, with their roles and profile limits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_team_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
queryNoMatches username or display name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the basic safety profile is known. The description adds value by specifying the scope ('current team account') and the output content ('roles and profile limits'), which is particularly helpful given there is no output schema. It does not contradict annotations.

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, front-loaded sentence. It immediately states the action and resource, then adds a concise detail about returned data. No wasted words.

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

Completeness4/5

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

For a simple list tool with strong annotations and no output schema, the description is mostly complete. It specifies what is returned and the scope. However, it does not mention pagination or filtering behavior, though these are inferable from the input schema parameters.

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 only 33% (only 'query' has a description). 'page' and 'limit' have no semantic explanation in the schema, and the tool description does not compensate by explaining pagination or the meaning of these parameters. The description adds no parameter-level guidance.

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 clearly states the action ('List') and the resource ('members of the current team account'), and adds specific output details ('with their roles and profile limits'). This distinguishes it from sibling tools like list_profiles or list_statuses.

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 the tool is for listing team members in the current team account, but it does not explicitly state when to use it versus alternatives or what situations it is not for. Sibling tools include create_team_user/update_team_user, but no cross-referencing or exclusion guidance is provided.

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