Skip to main content
Glama

set_schedule

Assign or remove due and start dates for one or more mind map elements, without inheriting parent dates, so tasks can be scheduled independently.

Instructions

要素の期日(due)と着手日(start)を付ける・外す。1件でも複数件でもよい。親の日付を子に引き継ぐことはしない(親と子の日付は独立している)。今の日付はlist_elementsで確認できる。

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": {
      "mapId": "<mapId>",
      "updates": "<updates>"
    },
    "name": "set_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapIdYeslist_mapsで得たマップのID
updatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / properties / updates / items / properties / due / description
      Previous value: -"終日なら\"YYYY-MM-DD\"、時刻付きなら\"YYYY-MM-DD HH:mm\"(このPCの現地時刻)。nullで外す。省略するとその日付には触れない"New value: +"終日なら\"YYYY-MM-DD\"、時刻付きなら\"YYYY-MM-DD HH:mm\"(アプリで設定しているタイムゾーンの時刻)。nullで外す。省略するとその日付には触れない"
  2. Addedv0.3.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden. It does disclose one important non-obvious behavior: parent dates are not inherited by children, so the sets are independent. Beyond that it says nothing about whether removing a date is destructive, whether the call is atomic if one elementId is invalid, or what happens on failures.

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?

Four short sentences, front-loaded with the action, then scope, then the key non-inheritance caveat, then the read-before-write pointer. No filler, though the parent/child sentence is repeated slightly in phrasing.

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?

For a two-parameter mutation tool with no annotations and no output schema, the definition covers what it changes and one important semantic caveat. It is still missing atomicity/partial-failure behavior, permission requirements, and any guidance versus edit_element, which an agent choosing between siblings would need.

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 coverage is reported at 50%, and the due parameter's schema already carries the format, null-to-remove, and omit-to-leave semantics. The description adds the batch notion ('1件でも複数件でもよい'), which tells the agent the updates array can group multiple elements in one call, but it says nothing about start and nothing about mapId beyond what the schema states.

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 specific verb pair (attach/remove) and a specific resource pair (due date and start date) on elements, and says it works for one or many. It is clearly distinguishable from list_elements, though it does not explicitly differentiate itself from edit_element, which plausibly touches similar fields.

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?

It points the agent at list_elements to read current dates before changing them, which is genuine usage guidance. However it gives no when-not conditions, no mention of edit_element as the alternative for other field changes, and no prerequisites (permissions, map ownership).

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