FronyBoard

set_overview

Create or replace a year's overview with a one-line goal plus now, target and checklist blocks, so quarterly milestones can be added later. Resend the checklist to keep it.

Instructions

Use it when the user sets or rewrites a year's plan (this year's goals, yearly plan).

Create or replace a year's overview: the one-line yearly `goal`, plus the three
blocks the dashboard shows for the current year — `now` (what is being worked on),
`target` (what that work is meant to reach) and `checklist` (the concrete steps to get
there, ticked off as they land). A year needs an overview before upsert_milestone will
add a quarter to it.

`year` is YYYY. All prose here is in the user's language. `now` and `target` are one
short line each. `checklist` items are strings (not done yet) or {text, done} maps,
in display order. Calling it again
replaces the whole overview — resend the checklist to keep it; use set_check to tick a
single item. Quarterly goals belong in upsert_milestone, not here.

Input Schema

Name	Required	Description	Default
`key`	Yes
`now`	No
`goal`	Yes
`year`	Yes
`target`	No
`checklist`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose the key destructive trait: calling it again replaces the whole overview, so the checklist must be resent to keep it. It also notes the prerequisite for upsert_milestone, but it does not describe authentication needs or the response/error behavior.

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?

The description is front-loaded with the usage trigger, then supplies the replacement semantics and parameter formats. Every sentence adds actionable information, and the formatting makes the key warnings easy to scan.

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?

For a mutation tool with six parameters, no annotations, and no output schema, the description covers purpose, alternatives, destructive replacement behavior, prerequisite ordering, and most parameter formats. The unexplained required `key` parameter and absent return-value context are the remaining gaps.

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 description coverage is 0%, so the description must compensate. It explains year as YYYY, goal as the one-line yearly goal, now and target as one short line each, and checklist as strings or {text, done} maps in display order — but it never explains the required `key` parameter.

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 description states a specific verb and resource: create or replace a year's overview with goal, now, target, and checklist. It explicitly distinguishes this from sibling tools by saying quarterly goals belong in upsert_milestone and single checklist ticks belong in set_check.

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?

It gives an explicit trigger — when the user sets or rewrites a year's plan — and names the alternatives for adjacent operations: set_check for ticking one item and upsert_milestone for quarterly goals. It also states the prerequisite that a year needs an overview before upsert_milestone can add a quarter.

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

set_overview

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools