Skip to main content
Glama
soil-dev

capsulemcp

by soil-dev
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

update_task

Update an existing task's fields: description, due date/time, detail, status (OPEN/COMPLETED), owner, or parent references. Only provided fields are changed; pass null on a parent to orphan the task.

Instructions

Update fields on an existing task: description, dueOn, dueTime, detail, status (OPEN or COMPLETED), ownerId, and the parent-reference fields partyId, opportunityId, projectId. Pass a parent id to re-link the task, or null on a parent field to orphan/unlink it; at most one parent id may be set in a single call, though null+id swaps are allowed. Only the fields you provide are changed. To mark a task done, prefer the dedicated complete_task tool — it's idempotent (a no-op success on an already-completed task) and semantically clearer than update_task status=COMPLETED. Capsule rejects directly setting status=PENDING (which exists only internally for track-driven tasks); use OPEN or COMPLETED. Completed tasks remain fully editable — Capsule does not enforce closed-record immutability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
descriptionNo
dueOnNoYYYY-MM-DD
dueTimeNoHH:MM in user's timezone
detailNo
statusNoSet to OPEN or COMPLETED. (PENDING exists internally for track-driven tasks but cannot be set directly via this tool — Capsule rejects it.) Setting status: OPEN on an already-open task is a true no-op (does not advance updatedAt).
ownerIdNoReassign owner to user ID. Once set, this connector cannot clear an owner back to null — use Capsule's web UI for that.
partyIdNoRe-link the task to a party by id, or `null` to orphan it. Mutually exclusive with `opportunityId` / `projectId` — Capsule enforces 'task can be related to at most one entity' server-side (422 if two parent-refs are set at once, verified in v1.6.3 wire-trace). To swap parent type atomically, pass the old one as `null` and the new one as an id in the same call. NOTE: orphaning is unique to tasks — `update_opportunity.partyId` and `update_project.partyId` are NOT nullable (Capsule rejects with 422 'party is required'). Tasks are the only entity in Capsule's data model that can exist without any parent.
opportunityIdNoRe-link the task to an opportunity by id, or `null` to orphan it. Mutually exclusive with `partyId` / `projectId` — see `partyId` for the XOR semantic.
projectIdNoRe-link the task to a project (kase) by id, or `null` to orphan it. Mutually exclusive with `partyId` / `opportunityId` — see `partyId` for the XOR semantic.

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Discloses that completed tasks remain editable, setting status OPEN on open task is a no-op, ownerId cannot be cleared, and detailed parent-reference behavior (nullable, swap allowed, uniqueness of tasks). No contradiction with annotations.

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?

Well-structured with clear front-loading. Slightly long but each sentence adds value. Could use bullet points but still effective.

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?

For a tool with 10 params and no output schema, the description covers all behavioral aspects: partial updates, idempotency, parent constraints, and contrasts with siblings. Complete for an update tool.

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

Parameters4/5

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

Adds significant context beyond schema: explains parent-field nullability and XOR, ownerId limitation, and status value restrictions. Schema coverage is 70%, but description compensates well.

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?

Clearly states 'Update fields on an existing task' and lists all updatable fields. Differentiates from sibling `complete_task` by noting it's the preferred way to mark a task done.

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

Usage Guidelines5/5

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

Explicitly says 'Only the fields you provide are changed' and recommends `complete_task` for marking tasks done. Warns about rejected status values and explains parent-reference XOR constraints.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/soil-dev/capsulemcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server