Skip to main content
Glama
Sign In
Alcove

Alcove

Official
by OctopusGarage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

alcove_routine_materialize_due

Generate tasks from recurring templates that are due today or on a specified date. Fill your task list with scheduled routine items.

Instructions

Create tasks for due recurring templates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "alcove_routine_materialize_due"
  }
}

Input Schema

NameRequiredDescriptionDefault
homeNo
todayNo
workspaceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

The description states 'Create tasks', implying a write operation, but lacks detail on side effects, idempotency, authentication requirements, or whether it modifies existing data. With no annotations, the burden is high, and this is not met.

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

Conciseness3/5

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

The description is a single concise sentence, which is efficient, but it sacrifices necessary detail. It front-loads the core action but omits important context.

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

Completeness2/5

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

Given the tool has 3 parameters with no documentation, no annotations, and sibling tools that overlap in function, the description is too sparse to fully guide an agent. The presence of an output schema is noted but not described, so the agent cannot anticipate return values.

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?

Zero% schema description coverage and the description adds no meaning to the three parameters (home, today, workspace). Their types and defaults are provided but not explained, leaving the agent to guess their role.

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

Purpose4/5

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

The description clearly states the action ('Create tasks') and the resource ('due recurring templates'), distinguishing it from sibling tools like alcove_task_add or alcove_routine_add. However, the term 'materialize' is slightly ambiguous and could be clarified with 'due today or in the future'.

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 on when to use this tool versus alternatives like alcove_task_add or alcove_routine_add. The description does not mention exclusions or prerequisites, leaving the agent to infer usage from the name alone.

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