Skip to main content
Glama

Nolio

Update a race, cycle, note or questionnaire

update_planned_event
Destructive

Change a planned competition, cycle, note or questionnaire. Only the fields you pass change. A change cannot be undone: say what will change and get the go-ahead first.

id: its pcmp_…, pcyc_…, pnot_… or pqz_… handle from get_calendar(mode='planned'). Name whose calendar carries it: athlete for a managed athlete's event, group for a group's event, neither for your own. The questions of a questionnaire cannot be changed here, and a questionnaire already answered cannot be changed at all. To change a description that is already set, send description_html: read the event first with get_calendar(mode='planned', with_description_html=true) over its date, edit only what must change, keep every other tag, and send the whole HTML back. Plain text description is refused there, because it would erase the coach's formatting.

Fields by type (any other field is refused):

  • competition (a race, the A-race being the main objective): sport (spt_… from list_sports, required), goal_type ('a' main goal, 'b' secondary), event (the race name), time (HH:MM) or moment (morning, noon, afternoon, evening), duration_minutes, distance_km, elevation_gain_m, elevation_loss_m, rpe (0-10), color.

  • cycle (a training block shown as a banner): date_end (YYYY-MM-DD, required on creation, on or after date_start), color. One cycle per period per athlete: an overlap is refused.

  • note (a marker on one day, or over a period with date_end): date_end (YYYY-MM-DD, on or after date_start, omitted = one day), note_type (rest, availability, unavailability, goal, menstruation), hour_start, hour_end (HH:MM), color. An availability also takes duration_minutes (the time available) and sports (spt_… from list_sports, [] clears them).

  • quiz (a questionnaire the athlete answers that day): hour_start (HH:MM, when it is sent, required for a group), and on creation exactly one of quiz_template (qzf_… from list_quiz_templates) or questions. Each question: {"question", "type", "is_mandatory", "choices", "unit", "metric"}; type is short_text, long_text, boolean, number (unit: kg, km, bpm, W… or a short free text), datetime (has_date, has_time), unique_choice (choices {"choices": [...]}, 2 or more), multiple_choices, range (choices {"start": 0 or 1, "advanced_captions": false, "captions": [...]}), metric_number or metric_range (metric: mti_… from list_metrics). Never an empty questionnaire. Every type takes name, date_start (YYYY-MM-DD) and description (plain text, accepted only while the event has no description).

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": {
      "type": "<type>",
      "id": "<id>"
    },
    "name": "update_planned_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
rpeNo
nameNo
timeNo
typeYes
colorNo
eventNo
groupNo
sportNo
momentNo
sportsNo
athleteNo
date_endNo
hour_endNo
goal_typeNo
note_typeNo
date_startNo
hour_startNo
descriptionNo
distance_kmNo
description_htmlNo
duration_minutesNo
elevation_gain_mNo
elevation_loss_mNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / sports
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description adds vital operational context beyond the annotations. It mandates a specific workflow for changing HTML descriptions—read, edit, send back the full HTML—which is a critical behavioral constraint not captured in the structured fields or hints.

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?

While the definition is extremely long due to the tool's complexity, it is highly organized using section headers and bullet points. This structure effectively manages the vast amount of information and prevents clutter.

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?

Given the complexity (4 resource types, 24 parameters, conditional requirements), the description is fully complete. It provides all necessary identifiers (`id` format), scoping rules (athlete vs. group), and all type-specific constraints required to invoke the tool correctly.

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?

With zero schema description coverage, the description is the primary source of meaning. It defines which fields belong to which `type`, explains domain concepts (e.g., goal types 'a' or 'b'), and provides syntax details like date formats (YYYY-MM-DD) and time formats (HH:MM).

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 identifies four specific resource types that can be updated: competition, cycle, note, and quiz. This clear scope, combined with the differentiation based on `type`, allows an agent to precisely determine its domain.

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?

The guidelines are extremely detailed, specifying behavior beyond a simple update function. It outlines non-undoability, rules regarding description formatting (HTML vs. plain text), and critical functional limits, such as preventing changes to answered quizzes or overlapping cycles.

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