mcp-server-hevy

Get Exercise Template

hevy_get_exercise_template

Read-onlyIdempotent

Retrieve a specific exercise template from Hevy by its ID to access detailed routine information for strength-training.

Instructions

One exercise template by id.

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": {
      "exerciseTemplateId": "<exerciseTemplateId>"
    },
    "name": "hevy_get_exercise_template"
  }
}

Input Schema

Name	Required	Description	Default
`exerciseTemplateId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 17, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. However, the description adds no additional behavioral context beyond 'by id'—it doesn't explain return behavior, error cases, or any side effects. This is thin even for a simple get-by-id tool.

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

Conciseness3/5

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

The description is a single fragment, making it concise and front-loaded. However, it is under-specified and the phrase 'one exercise template by id' largely restates the title, so it doesn't maximize the value of its brevity.

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?

Given the tool's simplicity (one parameter, no output schema) and strong annotations, a minimal description may suffice. Still, it omits what the returned template looks like or any mention of the search sibling, leaving some gaps even for a basic get-by-id operation.

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

Parameters2/5

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

Schema description coverage is 0% and the description only says 'by id,' which adds minimal meaning beyond the parameter name 'exerciseTemplateId.' It doesn't clarify the format, source, or expected value of the ID. The parameter name is self-explanatory, but the description does not compensate for the absence of schema-level documentation.

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 clearly identifies the resource ('One exercise template') and the retrieval scope ('by id'), which distinguishes it from sibling search tools like hevy_search_exercise_templates. It is specific but relies on the title for the verb, making it slightly less explicit than an ideal purpose statement.

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 phrase 'by id' implies use when you have a specific exercise template ID, but it provides no explicit guidance about when to prefer this over alternatives such as hevy_search_exercise_templates. No exclusions or conditions are stated, and the tool is not clearly differentiated from sibling read tools.

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

Deploy Server