Skip to main content
Glama
Sign In
Base.vn FastMCP Server

Base.vn FastMCP Server

by judestd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Base Account Set Group Managers

base_account_set_group_managers

Set the list of managers for a department or group on Base Account. Provide the group path and manager(s) to update who manages it.

Instructions

Thiết lập danh sách quản lý (Managers) cho một phòng ban / nhóm trên Base Account.

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": {
      "path": "<path>",
      "managers": "<managers>"
    },
    "name": "base_account_set_group_managers"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
managersYes
access_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 burden of behavioral disclosure. The description only says 'Thiết lập danh sách quản lý' (set the manager list), which implies a write operation, but it does not disclose whether this replaces the entire manager list, whether it requires specific permissions, whether it is reversible, or what the response contains. For a mutation tool with zero annotation coverage, this is a significant gap.

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

Conciseness4/5

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

The description is a single, concise sentence in Vietnamese that is front-loaded with the action and resource. It is appropriately sized for the tool's simplicity, though it could add a bit more context without becoming verbose.

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?

Given the tool has 3 parameters, no annotations, and an output schema, the description is incomplete. It does not explain the 'path' parameter, does not clarify whether 'managers' replaces or appends to the existing manager list, and does not describe the expected output. An agent would need to infer too much to invoke this tool correctly.

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 0%, so the description must compensate for the undocumented parameters. The description mentions 'danh sách quản lý (Managers)' which maps to the 'managers' parameter, but it does not explain the 'path' parameter (likely the group/department path) or the 'access_token' parameter. The description adds minimal value beyond the schema, leaving two of three parameters semantically unexplained.

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 states a specific verb ('Thiết lập' = set/configure) and resource ('danh sách quản lý (Managers) cho một phòng ban / nhóm trên Base Account'), which clearly identifies the action and target. It does not explicitly differentiate from sibling tools like base_wework_add_department_manager or base_wework_set_project_manager, but the resource (Base Account group/department) is distinct enough to avoid major confusion.

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 guidance on when to use this tool versus alternatives. It does not mention that this is for Base Account groups specifically, nor does it contrast with sibling tools like base_wework_add_department_manager or base_wework_set_project_manager. The context is implied by the tool name and description, but no explicit when/when-not guidance is given.

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