PutRoots

Where this move stands, in five numbers

move_plan

Read-only

The whole move at a glance for the signed-in person: days to move day, how many tasks there are, how many are settled, how many can be done right now, how many are blocked and how many are overdue, plus the critical path. Two rulers share that answer and they are not interchangeable: total and done count every task in the move, while actionable, blocked and overdue count only tasks that have been unlocked so far. Blocked therefore mixes two things — tasks missing an answer from the person, and tasks whose prerequisites aren't finished so they haven't been generated yet. Report the numbers as given; don't subtract one from another.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`d0`	Yes
`ok`	Yes
`done`	Yes	Settled: done, sent, called, replied or marked not applicable (full ruler).
`total`	Yes	Every task in this move (full ruler).
`health`	Yes
`blocked`	Yes	total - done - actionable: tasks missing an answer AND tasks not yet unlocked, together.
`overdue`	Yes	Past due, not in flight, not blocked (unlocked ruler).
`actionable`	Yes	Unlocked and not waiting on an answer (unlocked ruler).
`days_to_d0`	Yes
`critical_path`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint, so the safety profile is known. The description adds behavioral nuance: explains that blocked mixes two types, and instructs to report numbers as given without subtraction. This adds value beyond annotations.

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?

Dense but efficient; every sentence adds meaning, including the crucial 'don't subtract' instruction. Front-loaded with the purpose.

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?

Complete for a no-param read-only summary. Output schema exists, so return values are covered. Description explains the semantics of each number, which is essential for correct interpretation.

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?

No parameters exist, so the schema covers everything. Baseline 4 applies; description doesn't need to add parameter 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?

States a specific verb+resource: 'the whole move at a glance' for the signed-in person, enumerating the five numbers and critical path. Clearly distinct from sibling tools like move_tasks (which likely lists tasks) and move_events (events).

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?

Does not explicitly state when to use this vs alternatives, though it implies a quick overview. It does not name sibling tools or exclusion conditions. The description focuses on interpretation rather than routing.

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

All PutRoots tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?