Skip to main content
Glama
CSOAI-ORG

Pomodoro AI MCP

Official
by CSOAI-ORG
OverviewSchemaRelated ServersScoreDiscussions
Python

start_session

Starts a new Pomodoro focus session with optional task name and custom duration. Helps maintain focus and productivity.

Instructions

Start a new Pomodoro focus session. Optionally specify a task name and custom duration (default uses configured timer).

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need structured analysis or classification of inputs against established frameworks or standards.

When NOT to use: Not suitable for real-time production decision-making without human review of results.

Args: task (str): The task to analyze or process. duration_minutes (int): The duration minutes to analyze or process. api_key (str): The api key to analyze or process.

Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskNoDeep Work
duration_minutesNo
api_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

D1.6/5.0
Behavior1/5

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

The description claims the tool is read-only, stateless, and idempotent, which is factually incorrect for starting a session. This misrepresents the tool's actual behavior, likely copied from a different tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose and includes irrelevant sections (behavioral transparency, authentication, rate limits) that don't apply to starting a session. It lacks focus and contains repetitive information.

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

Completeness1/5

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

Given sibling tools like 'stop_session' and 'configure_timer,' the description should explain session lifecycle, default duration, task linking, and what 'default uses configured timer' means. It fails to provide any of this context, making it incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Parameter descriptions are generic placeholders ('The task to analyze or process') that add no value beyond the schema. With 0% schema description coverage, the description should compensate but fails to explain the purpose or constraints of each parameter.

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

Purpose3/5

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

The first sentence clearly states 'Start a new Pomodoro focus session,' which is a specific verb+resource. However, the subsequent description (read-only analysis, classification) contradicts this purpose, causing confusion.

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

Usage Guidelines1/5

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

The 'When to use' section suggests using it for structured analysis, which is inconsistent with starting a session. The 'When NOT to use' mentions real-time production decision-making, irrelevant to Pomodoro sessions. No guidance on session-specific use cases or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CSOAI-ORG/pomodoro-ai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server