Skip to main content
Glama

set_workout_plan_template_marketplace

List or unlist a workout plan template on the Trainzilla marketplace, and set its price (confirm-gated). This does not process any payment — it only makes the template available for other coaches to buy.

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": {
      "templateId": "<templateId>",
      "isMarketplace": "<isMarketplace>"
    },
    "name": "set_workout_plan_template_marketplace"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
currencyNo
templateIdYes
isMarketplaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, and the description adds that no payment is processed and that execution is gated. However, 'confirm-gated' largely restates the schema's confirm property, and it omits what happens to existing buyers or copies when a template is unlisted, and any permission requirements.

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?

Two tight sentences, front-loaded with the action and followed by the key scope caveat; little waste. The parenthetical 'confirm-gated' is slightly jargon-y but efficient.

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 5-parameter state-changing tool with 20% schema coverage and no output schema, the definition covers intent and the payment non-goal but omits currency handling, whether price is required when listing, and any return/confirmation semantics. Adequate but with real gaps.

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 coverage is only 20% (only confirm is documented), so the description must carry weight; it effectively explains price and the list/unlist binary implied by isMarketplace. It says nothing about templateId validation or, more importantly, how currency is supplied or defaulted when price is set, leaving one of five parameters undocumented in both places.

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 concrete verb set and resource ('List or unlist a workout plan template on the Trainzilla marketplace, and set its price'), so an agent knows exactly what state this changes. It does not, however, differentiate from the close sibling set_workout_plan_marketplace (whole plans vs templates), leaving a subtle ambiguity.

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?

It clarifies scope negatively ('does not process any payment') and notes the action is confirm-gated, which implies a preview-then-execute flow. It never says when to prefer this over set_workout_plan_marketplace or set_plan_listed, nor what prerequisites (e.g. template validity, currency) listing requires.

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.