Skip to main content
Glama

set_diet_plan_marketplace

List or unlist an existing diet 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_diet_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.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description adds real behavioral context: no payment is processed, the effect is limited to making the plan buyable, and the call is confirm-gated so it previews until confirm: true. What it does not state is the effect of unlisting on already-purchased buyers or whether the operation is reversible, which would round out the mutation profile.

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?

Three tight sentences with the core action and scope front-loaded, then the no-payment caveat, then the confirm-gating note. The parenthetical confirm reminder partially duplicates the schema's confirm description, but the rest of the text is dense and earns its place.

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 with no output schema and low schema coverage, the description covers the operation's nature and safety framing well but leaves key gaps: the meaning of isMarketplace, the currency parameter, and the relationship between price and usdPrice. An agent could invoke it correctly on the happy path but would be guessing on currency handling and on what a preview response contains.

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 only 17%, so the description carries real weight here, and it does explain price as whole currency units and usdPrice as the international-buyer price. It leaves the required isMarketplace boolean (which encodes list vs unlist) and the currency parameter uninterpreted, and gives no guidance on how price and usdPrice relate or which one wins.

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 specific verbs (list/unlist) plus the resource (an existing diet plan on the Trainzilla marketplace) and the additional act of setting price, which is enough to separate it from siblings such as set_diet_plan_template_marketplace or set_workout_plan_marketplace by resource noun alone. It stops short of explicitly naming any sibling as the wrong choice, so it is clear but not fully differentiated.

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?

Usage is implied by 'list or unlist an existing diet plan' and the clarification that it 'only makes the plan buyable', so an agent can infer this is the marketplace-visibility step rather than plan creation or editing. There is no explicit when-not guidance, no prerequisites (e.g. plan must exist, must be owned), and no named alternative for the template/workout variants.

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.