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

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
`sport`	No	what the event is: the plan builds toward it and get_event_course reads only a bike event in watts
`mapUrl`	No
`result`	No	what came of it, their words; '' clears
`target`	No	their aim; '' clears
`purpose`	No	why they race it: result (a win, a finish, a time — say which in target), training (it replaces a session, no taper), fun (purely for the joy); '' clears. Ask them once if unknown
`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.

Changed2 schema fields changedNov 2, 2026

changedInput schema / properties / sport / description

Previous value: -"ride or run — what the Course tab and get_event_course read the route for"New value: +"what the event is: the plan builds toward it and get_event_course reads only a bike event in watts"

changedInput schema / properties / sport / enum

Previous value: -[
-  "ride",
-  "run"
-]New value: +[
+  "ride",
+  "gravel",
+  "mtb",
+  "cx",
+  "tt",
+  "run",
+  "trail",
+  "triathlon",
+  "duathlon",
+  "swim",
+  "hyrox",
+  "ski",
+  "other"
+]

Changed3 schema fields changedOct 30, 2026

changedInput schema / properties / purpose / description

Previous value: -"why they race it: place (a position), time (a time or watts — say it in target), finish (to finish and enjoy it), training (a hard session, no taper); '' clears. Ask them once if unknown"New value: +"why they race it: result (a win, a finish, a time — say which in target), training (it replaces a session, no taper), fun (purely for the joy); '' clears. Ask them once if unknown"

changedInput schema / properties / purpose / enum

Previous value: -[
-  "place",
-  "time",
-  "finish",
-  "training",
-  ""
-]New value: +[
+  "result",
+  "training",
+  "fun",
+  ""
+]

addedInput schema / properties / result

Added value: +{
+  "description": "what came of it, their words; '' clears",
+  "maxLength": 200,
+  "type": "string"
+}

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / purpose

Added value: +{
+  "description": "why they race it: place (a position), time (a time or watts — say it in target), finish (to finish and enjoy it), training (a hard session, no taper); '' clears. Ask them once if unknown",
+  "enum": [
+    "place",
+    "time",
+    "finish",
+    "training",
+    ""
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 29, 2026

addedInput schema / properties / sport

Added value: +{
+  "description": "ride or run — what the Course tab and get_event_course read the route for",
+  "enum": [
+    "ride",
+    "run"
+  ],
+  "type": "string"
+}

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.5/5.0

Behavior4/5

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

Despite destructiveHint=true, the description clarifies patch semantics ('every field optional, only what you pass changes'), which materially reduces the risk of an agent wiping fields, and it discloses a non-obvious side effect: weather re-resolves on date/location change. It stops short of saying how a field is cleared (empty string) or what the call returns, which the schema partially covers.

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?

Three front-loaded sentences with the routing exclusions last, and almost no filler. The parenthetical field list is long and partly restates schema properties, but it earns its place as an at-a-glance roster for a 15-parameter tool.

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 15-parameter destructive mutation with no output schema, the description covers triggers, partial-update semantics, side effects, and sibling routing. Missing only clearing semantics and any note on what the response contains, which is tolerable given the schema's '' clears hints.

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?

At 53% schema description coverage the description must compensate, and it does by naming the field families an agent will most often edit (name, date, start time, description, location, URLs, logistics notes). The remaining enum-bearing semantics (cda, sport, purpose, priority) are handled by rich schema descriptions, so the split is coherent; it just doesn't tie the listed fields to the actual parameter names.

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?

Opens with a specific verb + resource ('Edit an existing event's fields') and enumerates the editable field roster, so the agent knows exactly the scope without opening the schema. It also explicitly names the sibling it is not (set_event_notes) and carves out prep content.

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?

'Use when the race date shifts, the venue changes, or details firm up' gives concrete trigger conditions rather than a vague intent. It then supplies both exclusions with named routing: coach notes go to set_event_notes, prep content is out of scope entirely.

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?