Skip to main content
Glama

Update event

update_event
DestructiveIdempotent

Changes the title, date, description, color, icon type, size, side of the line, text position, or link of one event or period in a timeline the user owns. Only the fields provided are changed.

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": {
      "timeline_id": "<timeline_id>",
      "event_id": "<event_id>"
    },
    "name": "update_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoLink to a reliable source or further reading, http or https, shown with the event or period; fits when sources are requested.
dateNoNew date of the event or new start of the period, as an ISO string. Years before Christ are negative. The month and the day can be omitted: "-0509", "1957-10", "1969-07-20".
typeNoTypes for an event: RECTANGLE: a rounded plate filled with the color, with the text inside; fits timelines of up to 15-20 events with room between neighboring dates. LINE: a thin stem from the line to the text, with no plate; the lightest look, fits a restrained style. CIRCLE: a dot on the line with the text beside it or above it; with LEFT or RIGHT its box is low. LINE and CIRCLE fit when there are more than 20 events or when events stand close together, so the labels do not pile up: LINE has the lowest and narrowest box, and CIRCLE with LEFT or RIGHT has a lower box than RECTANGLE. VERTICAL_RECT: a filled plate and a vertical line across the whole canvas height; very loud. VERTICAL_DOT: a dot and a vertical line across the whole canvas height; loud. VERTICAL_RECT and VERTICAL_DOT are for 1-3 turning points on the whole timeline. CIRCLE_IN: the text inside a filled circle that grows with the text; fits names of one to three words. Types for a period: RECT_TOP: a thin bar with the text under or above it; the name stays whole at any width. RECT_APPROX_TOP: RECT_TOP with fading edges on both sides. THIN: a 2-pixel line with the text under or above it; the most modest look, fits many overlapping periods. BRACES: a curly brace along the whole period with a light fill down to the line; fits eras and chapters that contain other objects. FILL_AREA: a thin line and a background band across the whole canvas height, drawn under everything else; fits the longest eras as a backdrop, at most three overlapping. RECT: a solid bar with the text inside, cut at the bar width. RECT_APPROX: RECT with fading edges on both sides ("roughly from ... to ..."). RECT_APPROX_LEFT: RECT with a fading left edge (the start is unknown). RECT_APPROX_RIGHT: RECT with a fading right edge (the end is unknown or it is still going on). By length: the longest eras fit FILL_AREA or BRACES; medium spans fit RECT_TOP or RECT_APPROX_TOP; short spans fit RECT_TOP or THIN; RECT, RECT_APPROX, RECT_APPROX_LEFT, and RECT_APPROX_RIGHT fit only periods that are long relative to the whole timeline and have short names.
colorNoColor as "#rrggbb": the fill of shapes with text inside, and the line and text of the others. Editor palette: #2c3d4d dark blue, #37a70b green, #96ec39 light green, #587934 olive, #1898e0 blue, #ffcca3 peach, #f56c00 orange. Text inside RECTANGLE, VERTICAL_RECT, CIRCLE_IN, RECT, RECT_APPROX, RECT_APPROX_LEFT, and RECT_APPROX_RIGHT gets a contrasting color from Time.Graphics. On the other types, the text has this color and lies right on the background: on the light background (#FCFCFC), #2c3d4d, #587934, #1898e0, #f56c00, and #37a70b read well, while #ffcca3 and #96ec39 are unreadable and fit only shapes with text inside. Pure black and pure white hide the hover highlight.
scaleNoSize of the object, a whole number from 10 to 1000; 100 is the normal size. It multiplies the font, the icon, and the padding. 120-150 fits 1-3 key events, 100 regular ones, and 70-85 small details in dense parts. Below 60 the text is unreadable; above 200 the object covers its neighbors. Objects of one category read best at one scale.
titleNoThe fact itself, 2 to 6 words, without the date: the axis shows the time. A name does not wrap on its own; "\n" separates lines. A line of up to 3 words reads best, and 2 words read better still: a 6-word name is three lines of 2 words each. In dense parts, one line of up to 3 words reads best.
date_toNoNew end of the period, in the same format as date; periods only.
event_idYes
over_lineNoSide of the line: true above it, false below it. The two sides stack independently. A plain list alternates sides; with two storylines, each keeps its own side (for example, politics above and culture below); background periods (FILL_AREA, BRACES) stay on one side.
descriptionNoText that opens in a separate window; it is not drawn on the timeline. Plain text: one or two sentences on why this matters, up to 300 characters, read best.
timeline_idYes
text_positionNoWhere the text stands relative to the icon; events only. CENTER: above or below the icon. CENTER fits when events are sparse: more than one-fifteenth of the length of the whole timeline lies between neighboring dates. When neighboring events are closer, CENTER labels stack on top of each other in tiers and run off the edge of the canvas. LEFT on the earlier event and RIGHT on the later one move the labels apart, to opposite sides. In a run of close events, the labels fit in a single row with the order LEFT, LEFT, RIGHT, RIGHT.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / color / description
      Added value: +"Color as \"#rrggbb\": the fill of shapes with text inside, and the line and text of the others. Editor palette: #2c3d4d dark blue, #37a70b green, #96ec39 light green, #587934 olive, #1898e0 blue, #ffcca3 peach, #f56c00 orange. Text inside RECTANGLE, VERTICAL_RECT, CIRCLE_IN, RECT, RECT_APPROX, RECT_APPROX_LEFT, and RECT_APPROX_RIGHT gets a contrasting color from Time.Graphics. On the other types, the text has this color and lies right on the background: on the light background (#FCFCFC), #2c3d4d, #587934, #1898e0, #f56c00, and #37a70b read well, while #ffcca3 and #96ec39 are unreadable and fit only shapes with text inside. Pure black and pure white hide the hover highlight."
    • addedInput schema / properties / date / description
      Added value: +"New date of the event or new start of the period, as an ISO string. Years before Christ are negative. The month and the day can be omitted: \"-0509\", \"1957-10\", \"1969-07-20\"."
    • changedInput schema / properties / date_to / description
      Previous value: -"only for periods"New value: +"New end of the period, in the same format as date; periods only."
    • addedInput schema / properties / description / description
      Added value: +"Text that opens in a separate window; it is not drawn on the timeline. Plain text: one or two sentences on why this matters, up to 300 characters, read best."
    • changedInput schema / properties / over_line / description
      Previous value: -"true above the timeline line, false below it"New value: +"Side of the line: true above it, false below it. The two sides stack independently. A plain list alternates sides; with two storylines, each keeps its own side (for example, politics above and culture below); background periods (FILL_AREA, BRACES) stay on one side."
    • changedInput schema / properties / scale / description
      Previous value: -"size, 100 is normal"New value: +"Size of the object, a whole number from 10 to 1000; 100 is the normal size. It multiplies the font, the icon, and the padding. 120-150 fits 1-3 key events, 100 regular ones, and 70-85 small details in dense parts. Below 60 the text is unreadable; above 200 the object covers its neighbors. Objects of one category read best at one scale."
    • changedInput schema / properties / text_position / description
      Previous value: -"only for events: text left or right of the icon, or CENTER above or below it (-1, 0, 1 in the style book)"New value: +"Where the text stands relative to the icon; events only. CENTER: above or below the icon. CENTER fits when events are sparse: more than one-fifteenth of the length of the whole timeline lies between neighboring dates. When neighboring events are closer, CENTER labels stack on top of each other in tiers and run off the edge of the canvas. LEFT on the earlier event and RIGHT on the later one move the labels apart, to opposite sides. In a run of close events, the labels fit in a single row with the order LEFT, LEFT, RIGHT, RIGHT."
    • addedInput schema / properties / title / description
      Added value: +"The fact itself, 2 to 6 words, without the date: the axis shows the time. A name does not wrap on its own; \"\\n\" separates lines. A line of up to 3 words reads best, and 2 words read better still: a 6-word name is three lines of 2 words each. In dense parts, one line of up to 3 words reads best."
    • changedInput schema / properties / type / description
      Previous value: -"icon type from the style book in timegraphics://guide: event types for events, period types for periods"New value: +"Types for an event: RECTANGLE: a rounded plate filled with the color, with the text inside; fits timelines of up to 15-20 events with room between neighboring dates. LINE: a thin stem from the line to the text, with no plate; the lightest look, fits a restrained style. CIRCLE: a dot on the line with the text beside it or above it; with LEFT or RIGHT its box is low. LINE and CIRCLE fit when there are more than 20 events or when events stand close together, so the labels do not pile up: LINE has the lowest and narrowest box, and CIRCLE with LEFT or RIGHT has a lower box than RECTANGLE. VERTICAL_RECT: a filled plate and a vertical line across the whole canvas height; very loud. VERTICAL_DOT: a dot and a vertical line across the whole canvas height; loud. VERTICAL_RECT and VERTICAL_DOT are for 1-3 turning points on the whole timeline. CIRCLE_IN: the text inside a filled circle that grows with the text; fits names of one to three words. Types for a period: RECT_TOP: a thin bar with the text under or above it; the name stays whole at any width. RECT_APPROX_TOP: RECT_TOP with fading edges on both sides. THIN: a 2-pixel line with the text under or above it; the most modest look, fits many overlapping periods. BRACES: a curly brace along the whole period with a light fill down to the line; fits eras and chapters that contain other objects. FILL_AREA: a thin line and a background band across the whole canvas height, drawn under everything else; fits the longest eras as a backdrop, at most three overlapping. RECT: a solid bar with the text inside, cut at the bar width. RECT_APPROX: RECT with fading edges on both sides (\"roughly from ... to ...\"). RECT_APPROX_LEFT: RECT with a fading left edge (the start is unknown). RECT_APPROX_RIGHT: RECT with a fading right edge (the end is unknown or it is still going on). By length: the longest eras fit FILL_AREA or BRACES; medium spans fit RECT_TOP or RECT_APPROX_TOP; short spans fit RECT_TOP or THIN; RECT, RECT_APPROX, RECT_APPROX_LEFT, and RECT_APPROX_RIGHT fit only periods that are long relative to the whole timeline and have short names."
    • addedInput schema / properties / url / description
      Added value: +"Link to a reliable source or further reading, http or https, shown with the event or period; fits when sources are requested."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the safety profile is covered. The description adds real value by stating that only supplied fields are modified, which softens the destructive framing, but it says nothing about permissions beyond ownership, whether prior values are recoverable, or how conflicting updates behave.

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?

Two sentences, no filler, with the mutation scope and partial-update rule front-loaded. The field enumeration is slightly redundant against a schema that already documents each field, but it works as a fast index of what can change.

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?

With 12 parameters and no output schema, the definition covers the write semantics but omits what is returned after a successful update and how failures (bad event_id, unauthorized timeline) surface. Adequate for a patch tool whose schema carries the heavy documentation, but not fully self-sufficient.

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 description coverage is 83%, so nearly every parameter is already richly documented in the schema, including the long type, color, and text_position guidance. The description only enumerates which fields are mutable and adds no format or constraint detail beyond that enumeration, so the baseline 3 applies.

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?

Names a specific verb (changes) and resource (one event or period), lists the mutable fields, and scopes it to a timeline the user owns. That separates it cleanly from the sibling write tools add_events and delete_events without needing their schemas.

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?

"Only the fields provided are changed" implies a partial-update use case and the ownership clause sets a precondition, but nothing states when to prefer this over add_events or delete_events, nor what happens if a field is omitted entirely. Usage must be inferred from the purpose sentence.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources