mcp-server-hevy

Search Exercise Templates

hevy_search_exercise_templates

Read-onlyIdempotent

Search exercise templates by name to fetch the exercise_template_id needed for creating workouts, using local filtering because Hevy has no server-side search.

Instructions

Find exercise templates by name to get the exercise_template_id needed for creating workouts/routines. Hevy has no server-side search, so this pages through templates and filters locally.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hevy_search_exercise_templates"
  }
}

Input Schema

Name	Required	Description
`query`	No	Case-insensitive substring of the exercise title.
`maxPages`	No
`pageSize`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds valuable context beyond this by disclosing that Hevy has no server-side search and that the tool pages through templates and filters locally, which explains potential performance and pagination behavior.

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 concise and front-loaded with the purpose, followed by a relevant caveat. Every sentence adds value, and there is no wasted text.

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 search tool with no output schema, the description covers the purpose and a key behavioral quirk (local filtering). However, it does not mention what the response contains (e.g., a list of templates with IDs), and it doesn't explain pagination parameters in enough detail. This makes it complete for a rough understanding but not fully self-sufficient.

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 only 33% (only 'query' has a description). The description mentions 'pages through templates' which implicitly relates to maxPages and pageSize, but it does not explicitly explain their behavior or how pagination works. Given the low coverage, the description should compensate more, but it leaves these parameters under-specified.

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 tool's purpose: to find exercise templates by name and retrieve the exercise_template_id needed for creating workouts/routines. It uses a specific verb ('Find') and indicates the resource and outcome, making it easy to understand what the tool does.

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

Usage Guidelines3/5

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

The description implies when to use this tool (when you need to search templates by name) and provides context about Hevy's lack of server-side search. However, it does not explicitly contrast with sibling tools like get_exercise_template, which fetches by ID, so guidance is present but not fully complete.

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

Deploy Server