Skip to main content
Glama

Find movements

find_movements
Read-onlyIdempotent

Movement slugs whose name holds query (e.g. "row", "sled"), for generate_workouts' include and exclude, machines and runs first.

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": {
      "query": "<query>"
    },
    "name": "find_movements"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoKeep one movement kind only, one of strength, olympic, plyo, cyclic, carry, mobility (cyclic: row, ski, bike, run); all when omitted. Example: "cyclic".
queryYesText the movement name holds, any case. Example: "sled".

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world. The description adds genuine value by disclosing the return form (slugs, not names) and a result ordering preference ('machines and runs first'), but says nothing about empty results, matching semantics, or ranking beyond that hint.

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

Conciseness4/5

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

A single dense sentence with the resource and purpose front-loaded and no filler. The trailing clause 'machines and runs first' is terse to the point of ambiguity about whether it describes ranking or filtering scope.

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

Completeness4/5

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

With an output schema, full parameter coverage, and rich annotations, the description only needs to convey purpose and downstream use, which it does. The main residual gap is result-ordering/matching behavior stated so compactly it may be misread.

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

Parameters3/5

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

Schema description coverage is 100%, so both `query` and `kind` are already documented with examples. The description's parenthetical examples ('row', 'sled') merely repeat the schema's own examples, adding no new meaning or syntax guidance.

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 states a specific resource and filter: movement slugs whose name contains `query`. It also names the downstream consumer (generate_workouts' include/exclude), which distinguishes it from siblings like list_equipment, though it never uses an explicit verb like 'search' or 'find'.

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?

It clearly explains the use case — resolving slugs to feed generate_workouts' include and exclude parameters — which is exactly the context an agent needs. It offers no when-not guidance or comparison to list_archetypes/list_equipment, so it falls short of full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources