Skip to main content
Glama

tasks_reconcile

Read-only

Reconcile Board proposal pass for Task OS. Scans active tasks, runs objective drift rules plus a bounded cheap classification pass, and returns proposed relationship/status/assignment/duplicate corrections. Proposal-only: applied is always false and this tool never changes tasks or edges. Review proposals and apply selected changes with tasks_update.

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": "tasks_reconcile"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID (UUID), subdomain, or slug, resolved server-side; 'default' is the organization's shared task board.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations say readOnlyHint=true and idempotentHint=false; the description reinforces non-mutation ('applied is always false and this tool never changes tasks or edges') and adds real behavioral context: a bounded cheap classification pass, drift rules, and that applying is a separate step. It doesn't explain what 'bounded' limits or what the proposal payload looks like, but with annotations covering safety, this is above baseline.

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?

Three tight sentences: what it does, what it returns, and what it does not do, followed by the next step. Front-loaded and every sentence earns its place.

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?

With one required parameter, full schema coverage, and read-only annotations, the description covers scope, output nature, and follow-up. Only the shape of proposals (fields, count limits) is left vague, which is acceptable given no output schema.

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?

Schema coverage is 100% and the schema already explains project_id resolution and the 'default' board. The description adds scope context ('scans active tasks') that helps the agent know what the project_id governs, though it doesn't add more per-parameter detail.

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?

Names a specific verb (Reconcile) and resource (Board proposal pass for Task OS), then enumerates what it scans and produces: relationship/status/assignment/duplicate corrections. It is clearly distinguishable from tasks_update, tasks_list, or tasks_get.

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 frames this as proposal-only review step and routes the agent to tasks_update for applying selected changes, which is the correct follow-up sibling. It also implies this is the scan-time tool rather than a direct mutation tool.

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