Skip to main content
Glama

reassign

by app.reassign
OverviewDiscussionsAdmin

Review a day

review_day
Destructive

Confirm or discard a whole day's reflection (by date, ISO YYYY-MM-DD), once you've marked its events with write_events' reflect op. action:"confirm" marks the day reviewed — "this is how it went" — freezing a per-day adherence snapshot (how closely actuals matched the plan, with per-area/per-type breakdowns), which get_schedule then returns as that day's review block and which the stats use; re-confirming refreshes it. action:"discard" fully resets the day: it removes the review, clears the kept/skipped/changed marks + actual times off the day's planned events (returned as updated), and deletes events ADDED only as part of the reflection (deletedIds) — use it to start a day's reflection over or drop one confirmed by mistake. Only a past day can be confirmed; discard works on any day, also on today's check-offs. A recorded undo receipt includes undoToken + expiresAt (UTC); call undo_changes before it expires. An empty discard returns noop:true, empty result arrays, and no undo receipt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
actionYes"confirm" freezes the day's adherence snapshot; "discard" fully resets the day's reflection (removes the review, clears every mark).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / llm_model
      Removed value: -{
-  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "date",
-  "action",
-  "llm_model"
-]New value: +[
+  "date",
+  "action"
+]
  2. Changed1 schema field changed
    • removedInput schema / properties / conversation_id
      Removed value: -{
-  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
-  "type": "string"
-}
  3. Changed4 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / conversation_id
      Added value: +{
+  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
+  "type": "string"
+}
    • addedInput schema / properties / llm_model
      Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "date",
-  "action"
-]New value: +[
+  "date",
+  "action",
+  "llm_model"
+]
  4. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / action / description
      Previous value: -"\"confirm\" freezes the day's adherence snapshot; \"discard\" fully resets the day's reflection (deletes the marker, clears every mark)."New value: +"\"confirm\" freezes the day's adherence snapshot; \"discard\" fully resets the day's reflection (removes the review, clears every mark)."
  5. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  6. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only give destructiveHint=true; the description goes far beyond by enumerating exactly what is destroyed (review, kept/skipped/changed marks, actual times, and reflection-added events returned in `deletedIds`), what is created (adherence snapshot with per-area/per-type breakdowns), and the undo lifecycle (`undoToken` + `expiresAt` UTC). It also discloses the no-op edge case (empty discard returns `noop:true`, empty arrays, no receipt).

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?

Front-loaded with purpose, then actions, then side effects and undo — a sensible information hierarchy in a single dense paragraph. It is long for a two-parameter tool, and the action descriptions echo the schema's enum text nearly verbatim, which is minor redundancy, but almost every clause carries operational information.

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

Completeness5/5

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

There is no output schema, and the description fills that gap by naming the returned fields (`updated`, `deletedIds`, `noop`, `undoToken`, `expiresAt`) and where the snapshot surfaces (`get_schedule`'s `review` block). For a destructive two-param mutation, everything an agent needs to call it safely and interpret the result is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% — `action` has an enum description but `date` has just a regex pattern with no prose. The description compensates by spelling out the ISO date format and, more importantly, elaborating the downstream consequences of each action value rather than restating the enum. It adds real meaning, though the date semantics are only lightly extended beyond the pattern.

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?

The description names a specific verb pair and resource ('Confirm or discard a whole day's reflection') and immediately scopes it with the required `date` param. It distinguishes itself from siblings by naming write_events' `reflect` op as the precondition and undo_changes as the follow-up, so an agent can separate this from get_schedule or delete_events without opening a schema.

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

Usage Guidelines5/5

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

Explicit preconditions ('once you've marked its events with write_events' `reflect` op'), explicit selection rules between the two actions, and explicit constraints ('Only a past day can be confirmed; discard works on any day'). It even names intended use cases — 'start a day's reflection over or drop one confirmed by mistake'.

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

All reassign 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