Lane Planner

Plan interests in lanes

plan_lanes

Read-onlyIdempotent

Use this for a first plan: the user lists several interests, projects or hobbies and asks for a plan for the next days or week, such as "10 hours a week for an app, a book, guitar and Japanese: plan my week". Input tips: send every interest with a short note, hours_per_week, and start_date as the user's local YYYY-MM-DD. Optional: days (3 to 7), days_off, next_steps for the build interest, lane when the user picked one, spine in the user's words. Returns the four lanes (build gets most minutes, reading is one chapter or paper, open is one side quest, the rest is parked with a bookmark), one spine sentence, the minute budget, the day plan with task ids, and todo_text to paste into a todo app. Tie-break with review_week: when an earlier plan or its text is in this chat, use review_week. Send done and not_done here only when the earlier plan is not in this chat and the user retells last week in words; then set lane on each interest to its lane last week. Not for a single task, a calendar booking or a diagnosis.

Input Schema

Name	Required	Description
`days`	No	How many days to plan, 3 to 7. Defaults to 7.
`done`	No	Only when the earlier plan is not in this chat and the user retells last week in words: the tasks they finished, such as ["set up the Xcode project"]. Then also set lane on each interest to the lane it had last week. The answer reviews that week and carries the missed build steps. If the earlier answer or its text is in the chat, use review_week instead.
`spine`	No	The user's own one-sentence direction that ties the interests together. Leave it out to get a first guess.
`days_off`	No	Weekdays with no tasks, as 3-letter names such as ["Sun"] or ["Sat", "Sun"]. At least one day of the plan must stay a work day.
`not_done`	No	Only with done, for a week retold in words: the tasks the user did not finish, such as ["local storage"].
`interests`	Yes	Every interest the user named, 1 to 12, in the order they gave them, such as [{"name": "Indie iOS app", "note": "ship a habit tracker"}, {"name": "Guitar"}].
`start_date`	No	First day of the plan as YYYY-MM-DD, such as "2026-10-08". Use today in the user's time zone, even mid-week; do not move it to a Monday or to tomorrow unless the user asked to start then. Defaults to today in UTC.
`hours_per_week`	Yes	Hours a week the user has for all of these together, 1 to 80, such as 10.

Output Schema

Name	Required	Description
`days`	Yes	The plan day by day, from start_date.
`lanes`	Yes	Each interest in its lane. Send this object back as review_week.lanes to review the week without the text.
`notes`	Yes	Short sentences on choices the tool made, such as a guessed spine or an interest moved to the parking lot. Often empty.
`spine`	Yes	The one sentence that points the lanes at the same direction.
`budget`	Yes	Minutes per lane over the whole plan; build, reading, open and review add up to total_minutes.
`review`	No	Only when done or not_done was sent. The count of last week's tasks. The review task itself is not counted.
`status`	Yes	Always ok; a call that cannot plan returns an error instead.
`changes`	No	Only when done or not_done was sent. Plain sentences on what the review changed for the next plan: carried build steps, a paused side quest, fewer hours, a swap from the parking lot. Tell them to the user.
`next_step`	Yes	What to tell or ask the user next.
`todo_text`	Yes	The plan as paste-ready text: header lines (Lane plan, Spine, the lanes, Parking lot), then one "- [ ] title (minutes) #id" line per task. Give it word for word; review_week reads it back.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

addedInput schema / examples

Added value: +[
+  {
+    "hours_per_week": 5,
+    "interests": [
+      {
+        "name": "Probe app",
+        "note": "ship a test build"
+      },
+      {
+        "name": "Probe book",
+        "note": "read one chapter"
+      }
+    ],
+    "start_date": "2026-10-12"
+  }
+]

Changed94 schema fields changedOct 11, 2026
- changedInput schema / properties / days_off / description
```
Previous value: -"Weekdays with no tasks, such as [\"Sun\"]."New value: +"Weekdays with no tasks, as 3-letter names such as [\"Sun\"] or [\"Sat\", \"Sun\"]. At least one day of the plan must stay a work day."
```
- addedInput schema / properties / days_off / uniqueItems
```
Added value: +true
```
- changedInput schema / properties / done / description
```
Previous value: -"Only when the user already had a lane plan: the tasks they say they finished, in their words. Set lane on each interest to last plan's lane. The answer then reviews that plan and carries the missed build steps."New value: +"Only when the earlier plan is not in this chat and the user retells last week in words: the tasks they finished, such as [\"set up the Xcode project\"]. Then also set lane on each interest to the lane it had last week. The answer reviews that week and carries the missed build steps. If the earlier answer or its text is in the chat, use review_week instead."
```
- changedInput schema / properties / hours_per_week / description
```
Previous value: -"Hours a week the user has for all of these together."New value: +"Hours a week the user has for all of these together, 1 to 80, such as 10."
```
- changedInput schema / properties / interests / description
```
Previous value: -"Every interest the user named, 1 to 12, in the order they gave them."New value: +"Every interest the user named, 1 to 12, in the order they gave them, such as [{\"name\": \"Indie iOS app\", \"note\": \"ship a habit tracker\"}, {\"name\": \"Guitar\"}]."
```
- changedInput schema / properties / not_done / description
```
Previous value: -"Only when the user already had a lane plan: the tasks they say they did not finish, in their words."New value: +"Only with done, for a week retold in words: the tasks the user did not finish, such as [\"local storage\"]."
```
- changedInput schema / properties / start_date / description
```
Previous value: -"First day of the plan as YYYY-MM-DD. Use today in the user's time zone, even mid-week: do not move it to a Monday or to tomorrow unless the user asked to start then. Defaults to today (UTC)."New value: +"First day of the plan as YYYY-MM-DD, such as \"2026-10-08\". Use today in the user's time zone, even mid-week; do not move it to a Monday or to tomorrow unless the user asked to start then. Defaults to today in UTC."
```
- addedOutput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / budget / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / budget / description
```
Added value: +"Minutes per lane over the whole plan; build, reading, open and review add up to total_minutes."
```
- addedOutput schema / properties / budget / properties / build / description
```
Added value: +"Minutes for the build lane."
```
- addedOutput schema / properties / budget / properties / build / minimum
```
Added value: +0
```
- addedOutput schema / properties / budget / properties / open / description
```
Added value: +"Minutes for the side quest; 0 when it is empty or paused."
```
- addedOutput schema / properties / budget / properties / open / minimum
```
Added value: +0
```
- addedOutput schema / properties / budget / properties / reading / description
```
Added value: +"Minutes for the reading lane; 0 when it is empty."
```
- addedOutput schema / properties / budget / properties / reading / minimum
```
Added value: +0
```
- addedOutput schema / properties / budget / properties / review / description
```
Added value: +"Minutes for the review task on the last work day."
```
- addedOutput schema / properties / budget / properties / review / minimum
```
Added value: +0
```
- addedOutput schema / properties / budget / properties / total_minutes / description
```
Added value: +"All planned minutes: the weekly hours scaled to the days of the plan."
```
- addedOutput schema / properties / budget / properties / total_minutes / minimum
```
Added value: +0
```
- addedOutput schema / properties / changes / description
```
Added value: +"Only when done or not_done was sent. Plain sentences on what the review changed for the next plan: carried build steps, a paused side quest, fewer hours, a swap from the parking lot. Tell them to the user."
```
- addedOutput schema / properties / days / description
```
Added value: +"The plan day by day, from start_date."
```
- addedOutput schema / properties / days / items / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / days / items / description
```
Added value: +"One day of the plan."
```
- addedOutput schema / properties / days / items / properties / date / description
```
Added value: +"The day as YYYY-MM-DD."
```
- addedOutput schema / properties / days / items / properties / items / description
```
Added value: +"The tasks of the day in order; empty on a day off."
```
- addedOutput schema / properties / days / items / properties / items / items / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / days / items / properties / items / items / properties / id / description
```
Added value: +"Task id, d<day>-<n>, such as \"d2-1\" for the first task of day 2. review_week accepts it in done or not_done."
```
- addedOutput schema / properties / days / items / properties / items / items / properties / minutes / description
```
Added value: +"Minutes for the task."
```
- addedOutput schema / properties / days / items / properties / items / items / properties / minutes / minimum
```
Added value: +1
```
- addedOutput schema / properties / days / items / properties / items / items / properties / tag / description
```
Added value: +"The lane of the task, or review for the weekly review task on the last work day. A carried build step keeps tag build and its title ends with \" (carried)\"."
```
- addedOutput schema / properties / days / items / properties / items / items / properties / tag / enum
```
Added value: +[
+  "build",
+  "reading",
+  "open",
+  "review"
+]
```
- addedOutput schema / properties / days / items / properties / items / items / properties / title / description
```
Added value: +"Task title that starts with its lane, such as \"Build: Indie iOS app: set up the Xcode project\"."
```
- addedOutput schema / properties / days / items / properties / minutes / description
```
Added value: +"Sum of the task minutes on this day."
```
- addedOutput schema / properties / days / items / properties / minutes / minimum
```
Added value: +0
```
- addedOutput schema / properties / days / items / properties / off / description
```
Added value: +"True on a day off; it has no tasks."
```
- addedOutput schema / properties / days / items / properties / weekday / description
```
Added value: +"The weekday as a 3-letter name."
```
- addedOutput schema / properties / days / items / properties / weekday / enum
```
Added value: +[
+  "Sun",
+  "Mon",
+  "Tue",
+  "Wed",
+  "Thu",
+  "Fri",
+  "Sat"
+]
```
- addedOutput schema / properties / lanes / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / lanes / description
```
Added value: +"Each interest in its lane. Send this object back as review_week.lanes to review the week without the text."
```
- addedOutput schema / properties / lanes / properties / build / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / lanes / properties / build / description
```
Added value: +"The build lane; there is always one."
```
- addedOutput schema / properties / lanes / properties / build / properties / minutes / description
```
Added value: +"Minutes this lane gets over the whole plan."
```
- addedOutput schema / properties / lanes / properties / build / properties / minutes / minimum
```
Added value: +0
```
- addedOutput schema / properties / lanes / properties / build / properties / name / description
```
Added value: +"Interest name, as the user gave it."
```
- addedOutput schema / properties / lanes / properties / build / properties / note / description
```
Added value: +"The user's note on it; empty when none was given."
```
- addedOutput schema / properties / lanes / properties / build / properties / time / description
```
Added value: +"The same minutes in words, such as \"6 h\" or \"1 h 30 min\", or \"none this plan\" when minutes is 0. Repeat it as is."
```
- addedOutput schema / properties / lanes / properties / build / properties / why / description
```
Added value: +"One sentence on why this interest has this lane."
```
- changedOutput schema / properties / lanes / properties / build / type
```
Previous value: -[
-  "object",
-  "null"
-]New value: +"object"
```
- addedOutput schema / properties / lanes / properties / open / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / lanes / properties / open / description
```
Added value: +"The open lane, or null when no interest fills it."
```
- addedOutput schema / properties / lanes / properties / open / properties / minutes / description
```
Added value: +"Minutes this lane gets over the whole plan."
```
- addedOutput schema / properties / lanes / properties / open / properties / minutes / minimum
```
Added value: +0
```
- addedOutput schema / properties / lanes / properties / open / properties / name / description
```
Added value: +"Interest name, as the user gave it."
```
- addedOutput schema / properties / lanes / properties / open / properties / note / description
```
Added value: +"The user's note on it; empty when none was given."
```
- addedOutput schema / properties / lanes / properties / open / properties / time / description
```
Added value: +"The same minutes in words, such as \"6 h\" or \"1 h 30 min\", or \"none this plan\" when minutes is 0. Repeat it as is."
```
- addedOutput schema / properties / lanes / properties / open / properties / why / description
```
Added value: +"One sentence on why this interest has this lane."
```
- addedOutput schema / properties / lanes / properties / parking_lot / description
```
Added value: +"Interests that wait this plan, each with a bookmark; nothing is dropped."
```
- addedOutput schema / properties / lanes / properties / parking_lot / items / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / lanes / properties / parking_lot / items / properties / bookmark / description
```
Added value: +"Where to pick it up next time."
```
- addedOutput schema / properties / lanes / properties / parking_lot / items / properties / name / description
```
Added value: +"Interest name."
```
- addedOutput schema / properties / lanes / properties / reading / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / lanes / properties / reading / description
```
Added value: +"The reading lane, or null when no interest fills it."
```
- addedOutput schema / properties / lanes / properties / reading / properties / minutes / description
```
Added value: +"Minutes this lane gets over the whole plan."
```
- addedOutput schema / properties / lanes / properties / reading / properties / minutes / minimum
```
Added value: +0
```
- addedOutput schema / properties / lanes / properties / reading / properties / name / description
```
Added value: +"Interest name, as the user gave it."
```
- addedOutput schema / properties / lanes / properties / reading / properties / note / description
```
Added value: +"The user's note on it; empty when none was given."
```
- addedOutput schema / properties / lanes / properties / reading / properties / time / description
```
Added value: +"The same minutes in words, such as \"6 h\" or \"1 h 30 min\", or \"none this plan\" when minutes is 0. Repeat it as is."
```
- addedOutput schema / properties / lanes / properties / reading / properties / why / description
```
Added value: +"One sentence on why this interest has this lane."
```
- addedOutput schema / properties / next_step / description
```
Added value: +"What to tell or ask the user next."
```
- addedOutput schema / properties / notes / description
```
Added value: +"Short sentences on choices the tool made, such as a guessed spine or an interest moved to the parking lot. Often empty."
```
- addedOutput schema / properties / review / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / review / description
```
Added value: +"Only when done or not_done was sent. The count of last week's tasks. The review task itself is not counted."
```
- addedOutput schema / properties / review / properties / by_lane / description
```
Added value: +"The same count per lane; a lane with no tasks last week is left out."
```
- addedOutput schema / properties / review / properties / by_lane / items / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / review / properties / by_lane / items / properties / done / description
```
Added value: +"Tasks done in this lane."
```
- addedOutput schema / properties / review / properties / by_lane / items / properties / done / minimum
```
Added value: +0
```
- addedOutput schema / properties / review / properties / by_lane / items / properties / lane / description
```
Added value: +"Lane name."
```
- addedOutput schema / properties / review / properties / by_lane / items / properties / lane / enum
```
Added value: +[
+  "build",
+  "reading",
+  "open"
+]
```
- addedOutput schema / properties / review / properties / by_lane / items / properties / not_done / description
```
Added value: +"Tasks not done in this lane."
```
- addedOutput schema / properties / review / properties / by_lane / items / properties / not_done / minimum
```
Added value: +0
```
- addedOutput schema / properties / review / properties / done / description
```
Added value: +"Tasks ticked or named as done."
```
- addedOutput schema / properties / review / properties / done / minimum
```
Added value: +0
```
- addedOutput schema / properties / review / properties / done_percent / description
```
Added value: +"done as a share of all tasks, 0 to 100. Under 40 means fewer hours next plan unless keep_hours is true."
```
- addedOutput schema / properties / review / properties / done_percent / maximum
```
Added value: +100
```
- addedOutput schema / properties / review / properties / done_percent / minimum
```
Added value: +0
```
- addedOutput schema / properties / review / properties / not_done / description
```
Added value: +"Tasks not done."
```
- addedOutput schema / properties / review / properties / not_done / minimum
```
Added value: +0
```
- addedOutput schema / properties / spine / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / spine / description
```
Added value: +"The one sentence that points the lanes at the same direction."
```
- addedOutput schema / properties / spine / properties / sentence / description
```
Added value: +"The spine sentence. Ask the user whether it fits."
```
- addedOutput schema / properties / spine / properties / source / description
```
Added value: +"given: the user's own words from spine. derived: a first guess from the lanes."
```
- addedOutput schema / properties / status / description
```
Added value: +"Always ok; a call that cannot plan returns an error instead."
```
- addedOutput schema / properties / todo_text / description
```
Added value: +"The plan as paste-ready text: header lines (Lane plan, Spine, the lanes, Parking lot), then one \"- [ ] title (minutes) #id\" line per task. Give it word for word; review_week reads it back."
```
First observedOct 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), and the description adds real behavior beyond them: the lane allocation rule (build gets most minutes, reading is one chapter or paper, open is a side quest, rest parked with a bookmark) and the conditional branch semantics tying done/not_done to setting lane on each interest.

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?

It is long and dense but deliberately structured into trigger, input tips, optional set, returns, tie-break routing, and exclusions, so an agent can scan for the clause it needs. Some duplication with the schema (done/not_done routing appears near-verbatim in both places) costs it the top score.

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 an 8-parameter planning tool with a nested interests object and an output schema, the description covers the call trigger, required and optional inputs, the conditional retelling path, and the routing alternatives to review_week. Nothing an agent needs in order to choose and call this tool correctly is missing.

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 100%, so the schema already documents all eight parameters in detail; the description's 'Input tips' and 'Optional' lines largely restate that coverage (hours_per_week, days 3-7, days_off, next_steps, lane). It adds only marginal framing, such as sending notes alongside every interest, so the baseline 3 is appropriate.

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 opening sentence names the specific trigger (user lists several interests and asks for a plan for the next days or week) and gives a concrete example utterance, so an agent can classify the request without opening the schema. It also differentiates itself from the sibling review_week by name and from single-task/booking/diagnosis requests in the final sentence.

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?

Explicit when-to-use (first plan), explicit tie-break routing to review_week when an earlier plan is in the chat, and explicit conditions for the done/not_done path when it is not. The closing exclusion list ('Not for a single task, a calendar booking or a diagnosis') removes the remaining ambiguity.

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

All Lane Planner 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.