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

Base.vn FastMCP Server

by judestd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Base Account Disable User

base_account_disable_user

Disable an employee's Base Account during offboarding to revoke access quickly.

Instructions

Vô hiệu hóa (disable) tài khoản nhân viên trên Base Account (offboarding).

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>"
    },
    "name": "base_account_disable_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYes
access_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

There are no annotations, so the description carries the full behavioral transparency burden. It only says 'disable', but does not explain the effect on login access, sessions, reversibility, or whether this is a destructive offboarding action.

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 one focused sentence with no filler, and the action is front-loaded. The parenthetical offboarding context adds useful meaning without bloating the text.

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 state-changing tool with no annotations and no parameter descriptions, this is too thin. It lacks behavioral consequences, setup requirements, and explicit differentiation from enable/update/delete-like sibling tools.

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, but it does not explain username or access_token semantics. The username is inferable, but access_token and required behavior are not clarified anywhere in the description.

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 states a specific action and resource: disabling an employee account on Base Account, with explicit offboarding context. It clearly distinguishes this from sibling tools like base_account_enable_user and base_account_update_user.

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 offboarding context implies when the tool should be used, but the description never explicitly says when not to use it or which alternatives to choose. It does not mention enable_user or update_user, leaving the selection largely to inference from the tool name.

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