Skip to main content
Glama
Sign In
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Update Custom Item

icu_update_custom_item
Idempotent

Update an existing custom chart, field, zones, or panel by item ID. Change only the supplied fields and leave all other settings unchanged.

Instructions

Modify an existing custom chart/field/zones/panel.

Use when the user wants to change one of their existing customizations: "rename my custom field", "make this chart public". Usually need icu_get_custom_items first to find the right item_id. Only fields you pass are sent — others are left unchanged. For content schema, see intervals-icu://custom-item-schemas.

Input Schema

NameRequiredDescriptionDefault
nameNoUpdated name
contentNoUpdated configuration content (replaces existing wholesale). Same schema as create_custom_item.content — see intervals-icu://custom-item-schemas for the per-item_type shape.
item_idYesCustom item ID to update
item_typeNoUpdated type (see icu_create_custom_item for values)
athlete_idNoAthlete ID (for coaches managing multiple athletes)
visibilityNoUpdated visibility: PRIVATE, FOLLOWERS, or PUBLIC
descriptionNoUpdated description

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.0
    • changedInput schema / properties / content / description
      Previous value: -"Updated configuration content (replaces existing content). Same schema rules as create_custom_item.content — for field-type items the inner shape is {`code`, `type`, `aggregate`} with the same validation constraints (code regex [A-Z][A-Za-z0-9]+, type in numeric/text/select, aggregate in MIN/SUM/MAX/AVERAGE)."New value: +"Updated configuration content (replaces existing wholesale). Same schema as create_custom_item.content — see intervals-icu://custom-item-schemas for the per-item_type shape."
    • changedInput schema / properties / item_type / description
      Previous value: -"Updated type (see create_custom_item for values)"New value: +"Updated type (see icu_create_custom_item for values)"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, so the safety profile is covered. The description adds a genuinely non-redundant behavioral fact — "Only fields you pass are sent — others are left unchanged" — clarifying partial-update semantics. It stops short of warning in prose that `content` is replaced wholesale (that lives only in the schema), which keeps it from a 5.

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?

Three short sentences, purpose front-loaded, examples inline, and the prerequisite and resource pointer placed after the core statement. No 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?

With an output schema, full annotation coverage, and 100% parameter descriptions, the remaining burden is purpose, timing, prerequisite, and mutation semantics — all present. Nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so baseline would be 3. The description goes beyond it by explaining the workflow for obtaining `item_id` and by clarifying that unspecified fields are untouched, which disambiguates the meaning of the nullable/defaulted parameters. The pointer to intervals-icu://custom-item-schemas for `content` adds further value.

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 resource set: "Modify an existing custom chart/field/zones/panel." This clearly separates it from icu_create_custom_item (new items) and icu_get_custom_items (reads) among the siblings.

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?

States the trigger condition with concrete user phrasings ("rename my custom field", "make this chart public") and adds a prerequisite: "Usually need icu_get_custom_items first to find the right `item_id`." That gives the agent both when-to-use and the ordering relative to a sibling.

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

Deploy Server

Other Tools