mcp-server-hevy

Search Hevy Capabilities

hevy_search_capabilities

Read-onlyIdempotent

Search for the right Hevy tool by query. Identifies the matching capability for your task, so you can proceed with the correct action.

Instructions

Find the right Hevy tool. Use first.

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_capabilities"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 17, 2026

TDQS

C2.3/5.0

Behavior2/5

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

The description adds no behavioral detail beyond the annotations, which already declare read-only, idempotent, and non-destructive. It does not disclose what the tool outputs, how it behaves, or any side effects. With no output schema, the agent has no understanding of the response.

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 extremely short and front-loaded, but its brevity is not concise—it is under-specified. It fails to provide essential information, making it less helpful than a slightly longer, complete description.

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

Completeness2/5

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

Given that this tool is meant to be used first, the description should explain what 'capabilities' are searched, what inputs do, and what output format to expect. It lacks all of this, and the absence of an output schema further reduces completeness.

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?

Schema description coverage is 0% and the description does not mention the 'limit' or 'query' parameters at all. The agent cannot infer what these parameters mean or how they affect the search, leaving a critical gap.

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

Purpose2/5

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

The description 'Find the right Hevy tool' vaguely suggests a discovery/search function, but it does not clearly state what the tool does or what it returns. It relies on the tool name 'search_capabilities' for any real meaning, making it close to a tautology.

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

Usage Guidelines4/5

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

'Use first.' is an explicit usage instruction indicating this tool should be invoked before others. However, it does not explain when not to use it or alternatives, so it stops short of a 5.

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

Deploy Server