Skip to main content
Glama

Coline

Add tasks to a project

add_tasks_to_project

Puts tasks in a project (optionally at a milestone) or takes them out. A task can be in several projects.

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>",
      "projectId": "<projectId>",
      "taskIds": "<taskIds>"
    },
    "name": "add_tasks_to_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoadd
taskIdsYes
projectIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
milestoneIdNo

Output Schema

NameRequiredDescriptionDefault
changedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description usefully discloses that membership is many-to-many and that removal only detaches from a project rather than deleting the task, but it leaves the idempotentHint=false behavior unexplained (what happens when a task already in the project is added again) and says nothing about required permissions on project or milestone.

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?

Two sentences, both earning their place, with the primary operation front-loaded and the many-to-many constraint as a supporting clause. No filler, no restatement of the title.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and annotations carry the mutation/safety signals. For a 5-parameter mutation with 20% schema coverage the description is nearly sufficient, with the main remaining gaps being the semantics of repeat-adds and per-parameter detail on projectId and taskIds.

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 description coverage is only 20%, so the description must carry weight: it does clarify the purpose of two otherwise bare parameters ('optionally at a milestone' for milestoneId, and 'takes them out' for action=remove). However, projectId and taskIds are left entirely to the schema, and the default action of 'add' and the 500-item cap are never surfaced.

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?

The description uses a concrete verb-plus-resource statement ('Puts tasks in a project ... or takes them out') and adds the key scope fact that a task can belong to several projects, so it is clearly distinguishable from project CRUD siblings like create_project or update_project. It stops short of naming any sibling explicitly, which keeps it at 4 rather than 5.

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: the add-or-remove framing tells the agent this is a membership operation rather than a task creation tool, and the milestone clause hints at the optional grouping case. There is no explicit 'use this when' / 'do not use this when' guidance and no named alternative for related operations such as filtering or listing tasks in a project.

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