Intervals.icu MCP Server

add_activity_message

Attach a note or comment to any Intervals.icu activity by providing its activity ID and message content.

Instructions

Add a message (note/comment) to an activity on Intervals.icu

Args: activity_id: The Intervals.icu activity ID content: The message text to add api_key: The Intervals.icu API key (optional, will use API_KEY from .env if not provided)

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": {
      "activity_id": "<activity_id>",
      "content": "<content>"
    },
    "name": "add_activity_message"
  }
}

Input Schema

Name	Required	Description	Default
`api_key`	No
`content`	Yes
`activity_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action and the optional API key behavior, but it does not mention side effects, duplicate behavior, permissions, error handling, or what the mutation returns.

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 compact and well-structured: a single purpose sentence followed by a focused Args list. Every line adds information, especially the environment fallback for api_key, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter tool with an output schema present, the parameter documentation and core action are adequate. However, the lack of when-to-use guidance and side-effect context, combined with zero annotations, keeps it at minimally viable rather than fully complete.

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%, but the Args block provides meaningful semantics for all three parameters: activity_id is the Intervals.icu activity ID, content is the message text, and api_key is optional with an explicit fallback to API_KEY from .env. This goes well beyond the bare schema titles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear verb+resource combination: 'Add a message (note/comment) to an activity on Intervals.icu'. This makes the tool's purpose unambiguous, though it does not explicitly distinguish itself from siblings like get_activity_messages or add_or_update_note.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for adding notes or comments to an activity but provides no explicit guidance on when to use it versus alternatives. Given the sibling list includes similar tools like get_activity_messages and add_or_update_note, explicit routing guidance is missing.

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