Skip to main content
Glama
Cafelatte1

FronyBoard

by Cafelatte1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

set_check

Mark a single roadmap checklist item done or undone by year and index, returning the updated overview for accurate project tracking.

Instructions

Use it when one item of the year's checklist is done or undone (tick off a checklist item).

Tick or untick one item of a year's overview checklist: `index` is its 0-based
position in get_roadmap's `checklist`, `done` the new state. Returns the updated
overview. To add, remove or reword items use set_overview.

Input Schema

NameRequiredDescriptionDefault
keyYes
doneNo
yearYes
indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that the tool returns the updated overview and that 'done' is the new state, but says nothing about permissions, idempotency, or what happens with an out-of-range index.

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?

Front-loaded with the usage condition, then the mechanics, then the alternative. Minor redundancy: 'tick off a checklist item' in parentheses restates the preceding clause.

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

Completeness3/5

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

For a no-annotation mutation tool with no output schema and 0% schema coverage, key gaps remain: the 'key' parameter is undefined and no failure modes are described. The reference to get_roadmap's checklist for index derivation is a helpful compensating detail.

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 coverage is 0%, so the description must compensate. It explains 'index' (0-based position in get_roadmap's checklist) and 'done' (new state) well, but leaves 'key' completely undocumented and 'year' only implied by 'a year's checklist.'

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 and resource: 'tick or untick one item of a year's overview checklist.' It also explicitly contrasts with set_overview for add/remove/reword, so an agent can distinguish it from siblings without opening schemas.

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?

Gives both the trigger condition ('when one item of the year's checklist is done or undone') and the exclusion with a named alternative ('To add, remove or reword items use set_overview'). This is explicit when/when-not routing.

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

Deploy Server

Other Tools