Skip to main content
Glama

run_cron

Manually advance the game day and apply damage from missed dailies. Use when the daily cron does not auto-run.

Instructions

Run the daily cron (advance day, apply damage from missed dailies). Normally auto-runs on first action of the day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool definition/schema for run_cron — describes the tool with no input parameters.
    // Cron
    {
      name: "run_cron",
      description: "Run the daily cron (advance day, apply damage from missed dailies). Normally auto-runs on first action of the day.",
      inputSchema: { type: "object", properties: {} },
    },
  • Handler that executes the run_cron tool by POSTing to the Habitica /cron API endpoint and returning success text.
    run_cron: async () => {
      await api("POST", "/cron");
      return ok("Cron run.");
    },
  • index.js:482-492 (registration)
    Generic MCP CallTool handler that dispatches to handlers[name]; run_cron is routed here via the handlers object.
    server.setRequestHandler(CallToolRequestSchema, async (req) => {
      const { name, arguments: args = {} } = req.params;
      const fn = handlers[name];
      if (!fn) throw new McpError(ErrorCode.MethodNotFound, `Unknown tool: ${name}`);
      try {
        return await fn(args);
      } catch (err) {
        if (err instanceof McpError) throw err;
        throw new McpError(ErrorCode.InternalError, err?.message ?? String(err));
      }
    });
Behavior4/5

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

With no annotations, the description adequately covers behavior: advancing day and applying damage. It also notes normal auto-run behavior. Could mention irreversibility, but core effects are clear.

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?

Two sentences, no wasted words. Front-loaded with the action, then context. Highly concise and structured.

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

Completeness5/5

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

For a parameterless tool with no output schema, the description fully explains purpose and normal behavior, leaving no gaps.

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?

Zero parameters and 100% schema coverage. Description adds no parameter info because none exist, baseline 4 is appropriate.

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?

Description clearly states the tool runs the daily cron, advancing day and applying damage from missed dailies. It uses a specific verb ('run') and resource ('cron'), and distinguishes from siblings as no other tool handles cron functionality.

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?

Mentions that it normally auto-runs on first action of the day, implying manual use is for exceptional cases. While it does not explicitly state when to use alternatives, the context is clear given no sibling does cron.

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/leon-jarvis1/habitca_mcp'

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