Skip to main content
Glama
AnonymousOnyx22

Study Planner MCP

by AnonymousOnyx22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Plan pomodoro sessions

plan_pomodoro_sessions
Read-only

Plan pomodoro study blocks from a total study time, separating work sessions with short breaks and a long break after a set number of sessions; add a start time to get clock times for each block.

Instructions

Plan pomodoro sessions for a total amount of study time: work blocks separated by short breaks, 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

A3.9/5.0
Behavior4/5

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

The description adds useful behavioral detail beyond the annotations: work blocks are separated by short breaks, a long break follows a set number of sessions, and start_time changes output from minute offsets to clock times. It does not describe every return detail, but with readOnlyHint=true and openWorldHint=true already indicating a safe read-only planning operation, the added context is meaningful.

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?

The description is front-loaded with the core purpose and progresses logically to start_time behavior and an example. It is efficient overall, though the example prompt is somewhat redundant given the preceding explanation. No sentence is seriously wasteful, but the example could be omitted without losing much.

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 6-parameter tool with only one required parameter, full schema coverage, and no output schema, the description covers the main behavior and the key optional start_time formatting choice. It does not explain edge cases like total_minutes limits, but the schema handles those. An agent has enough context to invoke the tool correctly.

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 input schema already documents all six parameters, including defaults and the start_time behavior. The description reinforces start_time with an example and explains the pomodoro structure, but it adds little parameter-specific meaning beyond what the schema already provides. Baseline 3 is appropriate.

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?

The description uses a specific verb and resource: plan pomodoro sessions for a total amount of study time. It clearly explains the structure of work blocks, short breaks, and long breaks. It does not, however, differentiate this tool from the very similar sibling pomodoro_plan, which leaves ambiguity for an agent choosing between them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context: provide total study time, optionally give start_time like 09:00, and receive clock times per block. The example prompt reinforces the intended invocation. It does not say when to prefer this over pomodoro_plan or make_study_plan, so it lacks explicit alternatives or exclusions.

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