Base.vn FastMCP Server

by judestd

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Base Account Create User

base_account_create_user

Creates a new employee account in Base.vn for onboarding new staff, using provided personal and job details.

Instructions

Tạo tài khoản nhân viên mới trên Base Account (onboarding nhân sự mới).

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>",
      "email": "<email>",
      "first_name": "<first_name>",
      "last_name": "<last_name>"
    },
    "name": "base_account_create_user"
  }
}

Input Schema

Name	Required	Description	Default
`dob`	No
`email`	Yes
`phone`	No
`title`	No
`units`	No
`gender`	No
`address`	No
`manager`	No
`password`	No
`username`	Yes
`last_name`	Yes
`first_name`	Yes
`access_token`	No
`direct_reports`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 10, 2026

TDQS

C2.3/5.0

Behavior2/5

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

No annotations are provided, so the description must carry behavioral disclosure. It states 'create new employee account' but does not disclose that the operation involves 14 parameters, requires an access_token, or indicate what happens on duplicate creation. No side effects or auth expectations are mentioned.

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

Conciseness2/5

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

The description is a single short sentence and technically concise, but it is concise because it omits nearly all useful information. There is no structure for the 14 parameters, no behavior details, and nothing beyond a restatement of the name in prose.

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

Completeness1/5

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

Given 14 parameters, a 0% schema description coverage, no annotations, and no usage guidance, this description is severely incomplete. The agent cannot determine required auth, field semantics, or side effects from the provided text. Output schema exists but does not compensate for the absence of operational context.

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

Parameters1/5

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

Schema coverage is 0% and the description adds no parameter information. With 14 parameters (including ambiguous ones like gender, units, direct_reports, and access_token), the agent receives zero guidance on what values are expected, constraints, or relationships between fields.

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 'Create employee account on Base Account (onboard new personnel)' clearly states a create operation for employee accounts, which distinguishes it from update/disable/enable siblings. It is specific enough about the action and resource, though it doesn't explicitly route around alternative tools.

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 on when to use this over siblings like base_account_update_user or base_account_enable_user. There is no mention of prerequisites (e.g., whether an access_token is required), no 'use X instead' notes, and no edge cases like duplicate usernames or onboarding flows.

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

Deploy Server