claw-mcp-toolkit

productivity_reminder

Create prioritized reminders with due dates to manage tasks and boost productivity. Set priority levels from low to critical and schedule deadlines for better time management.

Instructions

Create a reminder with priority level

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": {
      "task": "<task>"
    },
    "name": "productivity_reminder"
  }
}

Input Schema

Name	Required	Description	Default
`task`	Yes	What to remember
`due_date`	No	Due date (YYYY-MM-DD or 'today', 'tomorrow')	today
`priority`	No		medium

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 23, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, yet the description discloses no behavioral traits: it doesn't explain what happens when the reminder triggers, notification delivery methods, persistence/storage, or the behavioral difference between priority levels (critical vs low).

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

Conciseness4/5

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

Extremely brief at six words, with no redundant phrases. However, breverty sacrifices necessary context given the lack of annotations and sibling differentiation. Front-loaded but insufficiently informative for the complexity.

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?

Incomplete for a 3-parameter creation tool with no annotations and no output schema. Fails to explain default values (today, medium), priority semantics, or return behavior. Sibling overlap makes the omission of differentiation guidance particularly costly.

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?

With 67% schema coverage (task and due_date described, priority not described), the baseline is 3. The description mentions 'priority level' which loosely maps to the priority parameter, but adds no syntax details, format constraints, or semantic meaning beyond the schema's enum values.

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?

States a clear action (Create) and resource (reminder) with a specific feature (priority level). However, it fails to distinguish from siblings like productivity_calendar_event or productivity_note that also create time-bound productivity entries.

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?

Provides no guidance on when to use this tool versus productivity_calendar_event, productivity_note, or productivity_task_breakdown. No mention of prerequisites or trigger behavior.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.