Skip to main content
Glama
Sign In
productive-mcp-rb2

productive-mcp-rb2

by rubenlangeweg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_board

create_board

Create a board within a Productive.io project to group related tasks and improve workflow organization.

Instructions

Create a new board in a Productive.io project

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": {
      "project_id": "<project_id>",
      "name": "<name>"
    },
    "name": "create_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesThe ID of the project to create the board in
nameYesName of the board
descriptionNoDescription of the board

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-alpha.7

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false; description adds no extra behavioral context (e.g., permissions required, side effects, or return value).

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?

Single sentence, 10 words, no wasted text. Perfectly concise for the information conveyed.

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?

Simple creation tool with 3 parameters and no output schema; description lacks details on return value, side effects, or post-conditions, leaving gaps for the agent.

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

Parameters3/5

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

Schema coverage is 100%, so the description adds no additional meaning beyond what's in the schema. Baseline 3 is appropriate.

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?

Description clearly states the verb 'create', the resource 'board', and the context 'Productive.io project'. It effectively distinguishes from sibling tools like create_task or create_folder.

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 tool vs alternatives (e.g., create_task_list, create_page). No mention of prerequisites or when not to use it.

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