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

Base.vn FastMCP Server

by judestd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Base Wework Mark Task Done

base_wework_mark_task_done

Mark a Base Wework task as completed by providing its ID, setting the task status to Done.

Instructions

Đánh dấu hoàn thành một task trên Base Wework (status = 1 / Done).

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": {
      "id": "<id>"
    },
    "name": "base_wework_mark_task_done"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
access_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It transparently discloses the core side effect: setting the task status to 1 / Done. However, it does not mention permissions, idempotency, behavior if the task is already done, or any additional side effects such as logging or notifications.

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 efficient sentence that front-loads the action and includes the concrete target state. There is no filler or repetition of the title.

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

Completeness3/5

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

For a simple mutation tool, the description provides the essential operation and result state. However, it omits usage guidance and parameter documentation, and with no annotations it does not cover permission requirements or edge-case behavior. It is minimally viable but not fully complete.

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 needed to document parameters, but it does not. The 'id' is inferable as the task ID from context and 'access_token' is a common auth parameter, but nothing in the description explicitly declares their meaning or constraints.

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 ('Đánh dấu hoàn thành' = mark complete) on a specific resource (Base Wework task) and even specifies the resulting state (status = 1 / Done). This clearly distinguishes it from sibling tools like base_wework_edit_task or base_wework_get_task.

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 explains what the tool does but gives no guidance on when to use it versus related tools such as edit_task or create_task, and no exclusions or prerequisites. Usage context must be inferred entirely from the tool name and sibling list.

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