Skip to main content
Glama
Sign In
HomarUScc

HomarUScc

by kcdjmaxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

timer_schedule

Schedule one-shot, interval, or cron timers to trigger a defined prompt at the specified time or recurring schedule.

Instructions

Schedule a timer (cron, interval, or one-shot)

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": {
      "name": "<name>",
      "type": "<type>",
      "schedule": "<schedule>",
      "prompt": "<prompt>"
    },
    "name": "timer_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTimer name
typeYesTimer type: cron, interval, or once
promptYesEvent prompt/description when timer fires
scheduleYesCron expression, interval in ms, or ISO timestamp
timezoneNoTimezone for cron timers (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral details. It only states the action without covering side effects, persistence, return value, or overwrite behavior, making it insufficient for an agent to fully predict the tool's behavior.

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?

The description is a single concise sentence that front-loads the core purpose with no redundant words, perfectly sized for its content.

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?

The schema covers all parameters, but the description lacks any mention of return values or operational context such as how timers are managed after scheduling. Adequate for a simple tool but not highly informative.

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 baseline is 3. The tool description adds no additional parameter semantics beyond repeating the type values; the schema already explains each parameter adequately.

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 action ('Schedule') and the resource ('a timer'), and explicitly lists the three supported time types (cron, interval, one-shot), distinguishing it from the sibling tool timer_cancel.

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?

The description implies its use by listing timer types but does not explicitly state when to use it versus timer_cancel or other tools. No exclusions or alternative conditions are mentioned, so the guidance is implied rather than explicit.

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