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

productive-mcp-rb2

by rubenlangeweg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_task_details

update_task_details
Idempotent

Modify the title or description of an existing task by providing the task ID. At least one field (title or description) must be supplied.

Instructions

Update the title (name) and/or description of an existing task. At least one field must be provided.

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": {
      "task_id": "<task_id>"
    },
    "name": "update_task_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesID of the task to update (required)
titleNoNew title/name for the task (optional, but cannot be empty if provided)
descriptionNoNew description for the task (optional, use empty string to clear description)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-alpha.7

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds minimal behavioral info beyond usage constraint. No contradictions.

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 with no wasted words. Perfectly front-loaded with action and condition.

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

Completeness5/5

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

Given the tool updates only two fields and annotations cover safety, the description is complete. No output schema is needed.

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 description adds little extra. It clarifies that 'title' is also called 'name', but otherwise repeats schema info.

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 clearly states the verb 'Update', the resource 'existing task', and specific fields 'title (name) and/or description'. It distinguishes from sibling tools like update_task_status and update_task_assignment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a clear prerequisite: 'At least one field must be provided.' While it doesn't explicitly state when not to use or name alternatives, the context makes it unambiguous when to use 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