Skip to main content
Glama

Nolio

by io.nolio
OverviewDiscussionsAdmin

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.

  • 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).

Input Schema

NameRequiredDescriptionDefault
rpeNo
nameNo
timeNo
typeYes
colorNo
eventNo
groupNo
sportNo
momentNo
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. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark this as a non-read-only, non-destructive write operation; the description adds valuable behavioral detail beyond that, including overlap refusal for cycles, field refusal for invalid fields, name exceptions for template questionnaires, description acceptance rules, and undo semantics. No contradiction with annotations.

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?

The description is long but justified by 23 parameters and zero schema descriptions. It is front-loaded with key constraints and organized by event type, and every section provides actionable information rather than restating the name or schema.

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 tool's complexity, 0% schema description coverage, and the presence of an output schema, the description is complete enough to call the tool correctly. It covers audience rules, conditional requirements, per-type fields, ID sources, refusal conditions, and undo behavior.

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?

Schema description coverage is 0%, so the description carries the full parameter burden. It thoroughly documents all 23 parameters by event type, including requiredness, formats, accepted enum-like values, ID prefixes, question structures, and type-specific conditional rules.

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 and resource: planning a competition, cycle, note, or questionnaire on a planned calendar. It explicitly distinguishes itself from the closest sibling, create_planned_training, which handles planned workouts.

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 routing guidance to create_planned_training for workouts, defines the athlete-vs-group audience rules, lists required fields by event type, names lookup tools for IDs, and states undo behavior via delete_event. An agent can decide when and how to use it without inference.

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

All Nolio toolsInspect
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