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

Base.vn FastMCP Server

by judestd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Base Wework Get Custom Table

base_wework_get_custom_table

Retrieve the custom table or grid data linked to a specific task by providing its ID, returning the structured dataset for direct use in workflows.

Instructions

Lấy bảng dữ liệu tùy chỉnh (custom table / grid) của task.

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_get_custom_table"
  }
}

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.2/5.0
Behavior2/5

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

With no annotations provided, the description must carry the behavioral burden, but it only says 'get'. It does not disclose side effects, read-only behavior, error outcomes, empty-result handling, rate limits, or any other operational behavior beyond what the verb implies.

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 short, front-loaded sentence with no filler or redundancy. It uses a bilingual clause for clarity, but every part earns its place.

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?

The tool has a simple parameter set and an output schema, so return value details are not required. However, with no annotations and nearly no parameter guidance, the description is only minimally sufficient for an agent to call the 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%, and the description adds only the context that the data belongs to a task, indirectly implying `id` is a task identifier. It provides no meaning for `access_token` and does not fully compensate for the lack of schema-level documentation.

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 concrete verb ('Lấy bảng dữ liệu tùy chỉnh' / get custom table), identifies the resource as a task's custom table/grid, and distinguishes it from sibling tools like base_wework_get_task, get_task_comments, and get_task_logs.

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 is given on when to use this tool versus related alternatives such as base_wework_get_task or base_wework_get_task_logs. It also does not mention prerequisites, expected inputs, or conditions that should trigger this tool.

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