Skip to main content
Glama

set_workout_plan_marketplace

List or unlist an existing workout plan on the Trainzilla marketplace and set its price (whole currency units; usdPrice for international buyers). No payment is processed — it only makes the plan buyable. (confirm-gated: previews until confirm: true)

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": {
      "planId": "<planId>",
      "isMarketplace": "<isMarketplace>"
    },
    "name": "set_workout_plan_marketplace"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered; the description adds genuinely new traits — a confirm-gated preview-then-execute flow and the fact that no payment is processed. It does not say what happens to an existing listing's price on unlist or whether changes take effect immediately.

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, with the core action first and the operational caveats (no payment, confirm gate) in trailing clauses. The parenthetical '(confirm-gated: previews until confirm: true)' is slightly compressed and could sit more naturally, but nothing is padded.

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 6-parameter mutation tool with no output schema and thin schema documentation, the description covers the safety story and pricing units but omits the listing-state semantics the agent most needs: whether price is required to list, defaults for currency, and what the preview returns. Adequate but incomplete.

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 17% (only 'confirm' is documented in the schema), so the description has to carry the parameter weight. It clarifies price units (whole currency units) and usdPrice's purpose (international buyers), but leaves currency, isMarketplace, and the interaction between price/usdPrice/currency — e.g., which is required when listing — undefined.

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?

States a concrete verb pair ('list or unlist'), the exact resource ('an existing workout plan'), and the domain ('Trainzilla marketplace'), plus the secondary effect of setting price. The word 'existing' plus 'workout plan' implicitly separates it from the template and diet-plan variants in the sibling set.

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 establishes that this only makes a plan buyable and does not process payment, which frames the situation. It never states prerequisites (e.g., plan must be saved/published first), nor does it contrast with set_plan_listed or the template marketplace tool, so the agent must infer which of the near-identical siblings to choose.

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.