Skip to main content
Glama
smart-gym-mcp
by sla1k

smartgym_unarchive_routine

DestructiveIdempotent

Restore an archived SmartGym routine to your active routine list. Use it to reactivate a workout plan you previously archived, with an optional dry run to preview changes first.

Instructions

Bring an archived routine back to the active list.

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": "smartgym_unarchive_routine"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
routineYes

Output Schema

NameRequiredDescriptionDefault
noticeYes
dry_runYes
skippedYes
archivedYes
routinesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the description need not restate safety. However, it adds nothing beyond them: it does not explain what the destructive hint means for an unarchive, whether prior settings/order are preserved, or that dry_run defaults to true (making a naive call a no-op). For a state-changing tool with a non-obvious default, this is a meaningful gap.

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 front-loaded sentence with no wasted words, and the resource is stated first. Its brevity costs completeness rather than clarity, so it is efficient but arguably too terse for a mutating tool.

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?

An output schema exists, so return values need not be described, but the definition still omits critical operational detail for a mutating tool: the dry_run default, whether the operation is reversible, and error behavior for non-archived routines. Given two parameters and zero schema description coverage, the one-line description is not sufficient.

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 0%, so the description must carry semantics, and it only implies the 'routine' argument by naming the resource. The 'dry_run' parameter, with its counterintuitive default of true, is entirely unexplained in both schema and description. Partial compensation yields a below-baseline score.

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 gives a specific verb ('bring back') and resource ('an archived routine'), which is clearly distinct from smartgym_archive_routines. It stops short of naming siblings or contrasting with adjacent lifecycle tools like smartgym_apply_routine or smartgym_update_routine, but the purpose is unambiguous.

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?

There is no guidance on when this should be called versus alternatives, nor any precondition such as the routine actually being archived. It also omits that the call is safe-by-default via dry_run, so an agent has no cue about the intended invocation sequence.

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