Skip to main content
Glama
Sign In
cronometer-mcp

cronometer-mcp

by cphoskins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cancel_active_fast

Cancel an in-progress fast while preserving your recurring schedule. Stop an active fast now without disrupting future planned fasts.

Instructions

Cancel an active (in-progress) fast while preserving the recurring schedule.

Use get_fasting_history to find active fasts (is_active=true).

Args: fast_id: The fast ID of the active fast to cancel.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fast_id": "<fast_id>"
    },
    "name": "cancel_active_fast"
  }
}

Input Schema

NameRequiredDescriptionDefault
fast_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

A4/5.0
Behavior2/5

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

No annotations provided, and the description fails to disclose behavioral details such as side effects, permissions, or reversibility beyond preserving the schedule.

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?

Extremely concise with two short paragraphs and an Args section; front-loads purpose and provides essential context without waste.

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 simple tool with one parameter and an output schema, the description covers the core functionality and prerequisite step, though it omits edge cases on non-active fasts.

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 coverage is 0%, but the description adds meaning by specifying that fast_id must belong to an active fast, compensating for the lack of schema descriptions.

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 clearly states the verb 'cancel' and the resource 'active fast', and distinguishes from deleting the schedule by noting preservation of recurring schedule.

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?

Provides explicit guidance to use get_fasting_history to find active fasts, but does not mention when not to use or alternatives like delete_fast.

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