Skip to main content
Glama
Sign In
Alcove

Alcove

Official
by OctopusGarage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

alcove_routine_add

Create recurring task templates to automate repetitive tasks. Define title, schedule, and priority for daily, weekly, or custom intervals.

Instructions

Create a recurring task template.

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": {
      "title": "<title>"
    },
    "name": "alcove_routine_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
homeNo
tagsNo
notesNo
titleYes
next_dueNo
priorityNomedium
workspaceNo
every_daysNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are present, so the description must fully convey behavioral traits. It only says 'Create a recurring task template' without disclosing side effects (e.g., whether the template is saved, if it overrides existing ones, or return behavior). Minimal transparency.

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?

At 4 words, the description is overly terse and sacrifices informative value. It could include key parameter hints or usage notes without becoming verbose.

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 8 parameters (0% schema coverage) and no output schema details in the description, the tool is poorly documented. Even with an output schema existing, its contents are not described. The tool's behavior and parameter roles are left to inference.

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?

Schema coverage is 0%, and the description adds no information about parameters. With 8 parameters (home, tags, notes, next_due, priority, workspace, every_days) and only 'title' required, the description fails to explain their purpose or usage.

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 'Create a recurring task template,' with a specific verb and resource. This distinguishes from sibling tools like alcove_task_add (one-time tasks) and alcove_routine_list (listing routines).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., alcove_task_add for one-time tasks or alcove_routine_materialize_due for materializing due routines). The description lacks context for tool selection.

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