Skip to main content
Glama
AnonymousOnyx22

Study Planner MCP

by AnonymousOnyx22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Pomodoro plan

pomodoro_plan
Read-only

Plan study time as work/break blocks with short and long breaks, then convert them to clock times when a start time is provided.

Instructions

Plan pomodoro sessions: a work and break schedule for a total amount of study time, with a long break after a set number of sessions. Give start_time, like 09:00, to get clock times for each block. Example prompt: "Plan 3 hours of studying as pomodoro blocks with breaks."

Input Schema

NameRequiredDescriptionDefault
start_timeNoClock time the first block starts, like 09:00. Leave it out to list the blocks as minutes from the start.
work_minutesNoWork block length in minutes.
total_minutesYesTotal study time in minutes.
long_break_minutesNoLong break length in minutes.
short_break_minutesNoShort break length in minutes.
sessions_before_long_breakNoWork sessions before a long break.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.7
    • addedInput schema / properties / start_time
      Added value: +{
+  "description": "Clock time the first block starts, like 09:00. Leave it out to list the blocks as minutes from the start.",
+  "type": "string"
+}
  2. First observedv0.1.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description usefully indicates the return shape (clock times per block when start_time is given, otherwise minutes from the start), which matters because there is no output schema, but it says nothing about edge cases such as totals that don't divide evenly into work blocks.

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?

Two tight sentences front-load the purpose and the start_time behavior, followed by a short example prompt. The example is slightly redundant with the preceding sentence but is not wasteful.

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?

With six fully documented parameters and no output schema, the description does give the return concept needed to interpret results. However, it leaves the biggest ambiguity for an agent – how this differs from the sibling plan_pomodoro_sessions – entirely unaddressed.

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%, and the description mostly restates what the schema already documents, including the 09:00 example for start_time. Baseline 3 is appropriate since the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (plan) and resource (pomodoro sessions) and summarizes the output shape: a work and break schedule with a long break after a set number of sessions. It is clear on its own, but it does nothing to distinguish itself from the near-identical sibling 'plan_pomodoro_sessions'.

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?

Usage is only implied through an example prompt ('Plan 3 hours of studying as pomodoro blocks with breaks'). There is no guidance on when to prefer this over plan_pomodoro_sessions or when a pomodoro plan is the wrong choice versus a full study plan.

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