Blocks

update_event

Destructive

Edit an existing event's fields (name, date, start time, description, location, URLs, logistics notes) — every field optional, only what you pass changes. Use when the race date shifts, the venue changes, or details firm up. Weather re-resolves automatically when date or location changes. For the coach-notes section use set_event_notes; for prep content changes don't touch this.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`cda`	No	the rider's CdA for this race, m² (e.g. from estimate_cda, after the athlete agrees); 0 clears to the 0.32 default
`date`	No
`name`	No
`notes`	No	athlete logistics; empty string clears
`mapUrl`	No
`target`	No	their aim; '' clears
`eventUrl`	No
`priority`	No	A = season goal, B/C = on the way, '' clears
`startTime`	No	local start 'HH:MM'; '' clears
`description`	No
`locationText`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / cda

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 0.6,
+      "minimum": 0.15,
+      "type": "number"
+    },
+    {
+      "const": 0,
+      "type": "number"
+    }
+  ],
+  "description": "the rider's CdA for this race, m² (e.g. from estimate_cda, after the athlete agrees); 0 clears to the 0.32 default"
+}

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / startTime

Added value: +{
+  "anyOf": [
+    {
+      "description": "local start time HH:MM",
+      "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+      "type": "string"
+    },
+    {
+      "const": "",
+      "type": "string"
+    }
+  ],
+  "description": "local start 'HH:MM'; '' clears"
+}

Changed2 schema fields changedSep 26, 2026

addedInput schema / properties / priority

Added value: +{
+  "description": "A = season goal, B/C = on the way, '' clears",
+  "enum": [
+    "A",
+    "B",
+    "C",
+    ""
+  ],
+  "type": "string"
+}

addedInput schema / properties / target

Added value: +{
+  "description": "their aim; '' clears",
+  "maxLength": 200,
+  "type": "string"
+}

First observedSep 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is partly covered. The description adds genuine behavioral context beyond the schema: partial-update semantics ('only what you pass changes') and an important side effect ('Weather re-resolves automatically when date or location changes'). It does not state permission requirements or whether prior values are recoverable, so not a 5.

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?

Three dense sentences, front-loaded with the core action and field list, followed by usage triggers, a side-effect note, and sibling routing. No filler, and the most important scoping information comes first.

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

Completeness4/5

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

For a 12-param mutation tool with no output schema, the description covers action, patch semantics, side effects, and sibling routing, which is most of what an agent needs. Minor gaps remain on permission/auth requirements and the full clearing semantics that live only in the schema.

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 only 42% across 12 parameters, so the description should compensate more. It lists field groups and contributes the useful patch-semantics note ('every field optional, only what you pass changes'), but clear-to-default behaviors (e.g. cda=0, target '' clears) are documented in the schema rather than the description, leaving gaps.

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?

States a specific verb ('Edit') and resource ('an existing event's fields') and enumerates the editable fields, so an agent immediately knows scope. It also differentiates the tool from siblings by naming set_event_notes for coach notes and warning off prep-content edits.

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?

Gives concrete triggering conditions ('when the race date shifts, the venue changes, or details firm up') and explicit exclusions ('for the coach-notes section use set_event_notes; for prep content changes don't touch this'). Both when-to-use and when-not-to-use are covered with named alternatives.

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

All Blocks tools Inspect

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

Need Help?