Skip to main content
Glama

Nolio

Plan a race, cycle, note or questionnaire

create_planned_event

Plan a competition, a cycle, a note or a questionnaire on a planned calendar. Planned workouts go through create_planned_training instead.

Audience: athlete (one managed athlete's usr_… handle) or group (a grp_… you manage, one event the whole group sees), never both; neither plans it on your own calendar. name is required, except for a questionnaire planned from a template (it takes the template's name). Undo a creation with delete_event on the returned id.

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>",
      "date_start": "<date_start>"
    },
    "name": "create_planned_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
rpeNo
nameNo
timeNo
typeYes
colorNo
eventNo
groupNo
sportNo
momentNo
sportsNo
athleteNo
date_endNo
hour_endNo
goal_typeNo
note_typeNo
questionsNo
date_startYes
hour_startNo
descriptionNo
distance_kmNo
quiz_templateNo
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

A5/5.0
Behavior5/5

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

Annotations only state write/non-destructive/closed-world; the description adds real behavioral context beyond them — unknown fields are refused, a cycle overlapping the same period is refused, an empty questionnaire is refused, and `description` is only accepted while the event has no description. It also documents recovery via delete_event and the one-cycle-per-period invariant.

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?

Front-loaded with purpose and the sibling exclusion, then organized into scannable per-type bullet blocks that map one-to-one onto the `type` enum. Length is justified by 24 parameters with no schema documentation; no sentence is filler.

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 24-parameter polymorphic create tool this is essentially complete: audience resolution, required fields, per-type conditional requirements (quiz_template XOR questions, date_end for cycles, hour_start for group quizzes), refusal semantics, and the undo path. Return values need no explanation because an output schema exists.

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 0% schema description coverage across 24 parameters, the description carries the full burden and does so: it maps every field to its type, gives identifier prefixes (spt_, qzf_, mti_) and their lookup siblings (list_sports, list_quiz_templates, list_metrics), enumerates note_type and goal_type values, spells out the question object shape and each question type's constraints, and states date_end >= date_start. Only `color` lacks a format note.

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 and the four resource types it creates, then immediately names the sibling it is *not* (create_planned_training) for planned workouts. An agent can route between the two creation tools 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?

Gives explicit when/when-not rules: workouts go to create_planned_training, undo goes through delete_event on the returned id, and audience is exactly one of athlete/group with neither meaning your own calendar. Per-type field rules tell the caller precisely which configuration path applies.

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