Skip to main content
Glama

Coline

Create a board

create_taskboard

Creates a task board, with default statuses (Backlog, Todo, In progress, Done) unless statuses are given.

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": {
      "workspace": "<workspace>",
      "title": "<title>"
    },
    "name": "create_taskboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
grantsNo
driveIdNo
parentIdNo
statusesNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
accessModeNo
descriptionNo
customFieldsNo
clientRequestIdNoSend the same id on a retry to avoid a second board.
identifierPrefixNoLetters before task numbers, like ENG in ENG-12.

Output Schema

NameRequiredDescriptionDefault
urlYes
nameYes
taskboardIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare this is a non-read-only, non-idempotent, non-destructive create. The description adds genuine value by disclosing that four default statuses are created unless overridden, which is real behavioral context. However, it says nothing about permission/grants implications of creation or what accessMode does.

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?

A single compact sentence with the key defaulting behavior front-loaded and zero filler. It is arguably too terse for an 11-parameter mutation, but nothing it says is wasted.

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 create tool with 11 parameters at 27% schema coverage and meaningful concepts like grants, accessMode, and customFields, the description is far too thin; an agent would have to guess at permissions and scoping semantics. The existence of an output schema excuses it from explaining return values, but not from explaining the request surface.

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 coverage is only 27% across 11 parameters, so the description must compensate and does not. Only the statuses parameter's defaulting behavior is explained; grants, driveId, parentId, accessMode, customFields, and description are left entirely to the bare schema, where several have no description string at all.

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?

States a specific verb and resource: "Creates a task board." It implicitly distinguishes itself from the many other create_* siblings (create_doc, create_sheet, create_project) by naming the resource, but it never explicitly contrasts with update_board or other board tools.

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?

Usage is only implied by the verb — an agent can infer this is the entry point for making a new board, versus read_taskboard/show_board for reading. There is no explicit when-to-use or when-not-to-use guidance, and no mention of prerequisites such as needing a workspace.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources