hevy-mcp

create_routine

Build a custom workout routine by specifying title, exercises, sets, and notes. Define exercise templates, set types, reps, weights, and rest periods for each exercise.

Instructions

Create a new routine

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": {
      "routine": "<routine>"
    },
    "name": "create_routine"
  }
}

Input Schema

Name	Required	Description	Default
`routine`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.1/5.0

Behavior1/5

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

Since no annotations are provided, the description carries the full burden of disclosing side effects and behavioral traits. It merely restates the tool name with no mention of what creation entails, whether it is reversible, or what side effects occur, providing zero transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very brief, but this brevity is under-specification rather than effective conciseness. For a tool with a complex nested parameter structure, four words do not provide adequate information, making the brevity a deficiency.

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

Completeness1/5

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

Given the complex input schema with nested objects and required fields, and the absence of an output schema, the description is severely incomplete. It provides no indication of return values, required fields, or expected behavior, making it inadequate for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description makes no reference to the 'routine' parameter or its nested structure. With schema description coverage at 0%, the agent gains no additional meaning from the description beyond the raw JSON schema, which is insufficient for proper invocation.

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 'Create a new routine' clearly states the action (create) and resource (routine), providing a specific verb and object. However, it does not differentiate from sibling tools like create_workout or update_routine, so it stops short of a top score.

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 offers no guidance on when to use this tool versus alternatives such as create_workout or update_routine. It lacks any context about prerequisites, use cases, or exclusions, leaving the agent to infer applicability on its own.

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