Skip to main content
Glama
Sign In

Blocks

by zone.blocks
OverviewDiscussionsAdmin

set_day_note

Destructive

Pass replaces (the start of ONE of YOUR OWN notes on that day — they come back with by:"ai") to rewrite that one note with note, or remove it with an empty note; the athlete's notes are never touched. Otherwise: ADD a SHORT note to a calendar day — a few words capturing the key thought (e.g. "easy week, watch sleep"), NOT an essay. A day holds SEVERAL notes; this appends one and never touches the athlete's own notes on that day. Max 1000 chars, but keep yours brief; the athlete uses the long form for their own impressions of the day. For a LIST they will tick off (race kit, the evening before a test) use add_checklist, not this. Pass an empty string to clear ALL notes on that day. Optional colour tags the note — the athlete assigns the meaning of each colour themselves, so only set it when they've told you what a colour means, or reuse a colour already on that day.

Input Schema

NameRequiredDescriptionDefault
dateYes
noteYes
colorNooptional colour tag; omit to leave the note uncoloured
replacesNothe start of one of YOUR OWN notes on that day: rewrite it (note) or remove it (empty note)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / replaces
      Added value: +{
+  "description": "the start of one of YOUR OWN notes on that day: rewrite it (note) or remove it (empty note)",
+  "maxLength": 200,
+  "minLength": 4,
+  "type": "string"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true/openWorldHint=false annotations by spelling out the exact destructive surfaces: an empty `note` with `replaces` removes one note, an empty string clears ALL notes that day, the athlete's own notes are never touched, appends are additive to several notes, and there is a 1000-char ceiling. This is precisely the detail an agent needs before a destructive call.

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?

Every clause earns its place given the multi-mode behavior, but it is a single dense run-on paragraph with em-dashes, and it front-loads the less common `replaces` path before the primary add-note action. Slightly harder to scan than ideal, though nothing is wasted.

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?

For a 4-parameter mutation tool with no output schema, the description covers modes, mutation semantics, character limits, the colour-tag convention, and sibling routing. Nothing an agent needs to call it safely and correctly is missing.

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

Parameters5/5

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

Schema coverage is only 50%, and the description compensates: it explains that `note` should be brief rather than merely maxLength 1000, that an empty `note` is the delete signal, that `replaces` is the prefix of one of your own notes (identified by the `by:"ai"` marker) and drives rewrite-vs-remove, and that `color` is an athlete-defined tag to use only when the meaning is known or already in use.

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?

Specific verb+resource ('set day note') with three clearly delineated modes: rewrite/remove an existing note via `replaces`, append a new short note otherwise, or clear all notes with an empty string. It explicitly differentiates from the sibling `add_checklist`, so an agent can route correctly without opening either 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?

States when to use this tool (short thought of a few words), when not to (tick-off lists such as race kit or the evening before a test belong to `add_checklist`), and what the athlete's own long-form notes are reserved for. The alternative and the selecting condition are both named.

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

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