Skip to main content
Glama
Sign In

OTP

by io.github.david-steel
OverviewDiscussionsAdmin

Set how a to-do repeats

set_todo_repeat
Destructive

Make a to-do repeat, change how a repeating to-do repeats, or stop it. Copies already finished or overdue keep their dates.

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": {
      "todo_id": "<todo_id>"
    },
    "name": "set_todo_repeat"
  }
}

Input Schema

NameRequiredDescriptionDefault
stopNotrue: stop the series. This copy stays as a normal to-do; copies already made ahead of their date are removed.
repeatNoThe new repeat settings. A one-off becomes a series; a series gets the new settings from here on.
todo_idYesThe to-do, or any copy of a repeating series.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true, so the safety bar is lower, and the description usefully adds that finished/overdue copies keep their dates. However, it does not disclose that stopping a series removes copies already made ahead of their date (a significant destructive side effect that appears only in the schema), which is a real gap for a destructive tool.

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 tight sentences with no filler; the core operations are front-loaded and the copy-date caveat is a single supporting clause.

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?

Given a complex nested schema and no output schema, the description is adequate because the schema covers parameters exhaustively. But for a destructive recurring-series tool it omits the removal-of-upcoming-copies consequence of stopping and gives no pointer to related tools, leaving meaningful operational context missing.

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% and the nested repeat object is documented thoroughly, so parameter meaning is fully carried by the schema. The description adds no parameter-level detail beyond what is already given, so baseline 3 applies.

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 specific verb modes (make repeat, change repeat, stop it) on a clearly named resource (a to-do). It's easy to identify what it does, but it doesn't distinguish itself from siblings like update_todo or the schedule tools, so an agent could reasonably wonder which one governs recurrence.

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?

Usage is implied by the three operations (create/change/stop a repeat), but there is no explicit guidance on when to use this versus update_todo or create_schedule/update_schedule, nor any stated precondition (e.g. that the to-do must exist).

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

All OTP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources