Skip to main content
Glama
hhopke
by hhopke

icu_create_custom_item

Add custom fields, charts, zones, or tables to your Intervals.icu account. Choose the item type to match your need—input fields for wellness, activity fields, interval fields, zone sets, or various chart types.

Instructions

Create a custom addition to the user's Intervals.icu account.

Use when the user says things like: "add a custom field for RPE", "create a custom power zone set", "add a chart for monthly distance". Match the user's intent to the right item_type (see that param's description). For the content schema per item_type, read intervals-icu://custom-item-schemas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name (e.g., 'RPE', 'Bike Weight', 'Custom Power Zones')
item_typeYesWhat the user wants to add. Pick by intent: INPUT_FIELD (extra input on the wellness page, e.g. RPE, mood), ACTIVITY_FIELD (extra field on each activity, e.g. bike weight), INTERVAL_FIELD (extra field on each interval), ZONES (custom power/HR/pace zone set), FITNESS_CHART / TRACE_CHART / FITNESS_TABLE (custom dashboard chart/table), ACTIVITY_CHART / ACTIVITY_HISTOGRAM / ACTIVITY_HEATMAP / ACTIVITY_MAP / ACTIVITY_PANEL (custom visual on the activity page), ACTIVITY_STREAM (computed time-series). Use the literal API value.
descriptionNoOptional description shown to the user
contentNoConfiguration object whose schema depends on item_type. Read intervals-icu://custom-item-schemas BEFORE constructing — it documents the {code, type, aggregate} shape required for INPUT_FIELD / ACTIVITY_FIELD / INTERVAL_FIELD (with constraints and worked examples) and explains that chart/panel/zones/stream types should omit `content`.
visibilityNoWho can see it: PRIVATE (default, only you), FOLLOWERS, or PUBLIC.
athlete_idNoAthlete ID (only for coaches; uses configured default otherwise)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate non-read-only and non-destructive behavior. The description adds context about reading external schemas but does not disclose additional traits like permission requirements, rate limits, or side effects beyond creation.

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 three sentences long with no wasted words. It front-loads the purpose, then provides usage examples, and finally directs to additional resources. Perfectly concise.

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?

Given the tool's complexity (multiple item types with varying content schemas), the description covers core usage and points to external resources for details. It does not explain return values, but an output schema exists. A minor gap is the lack of error handling or prerequisites.

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?

Schema description coverage is 100%, so baseline is 3. The description adds value by pointing to intervals-icu://custom-item-schemas for the content parameter, which is essential for correct usage.

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 clearly states the verb 'Create a custom addition' and specifies the resource 'user's Intervals.icu account'. It provides examples of user intents, making it easy to distinguish from sibling tools like icu_update_custom_item.

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 description explicitly tells when to use the tool by listing example user statements ('add a custom field for RPE', etc.) and advises matching intent to item_type. It also references an external schema for content construction, providing clear context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hhopke/intervals-icu-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server