Skip to main content
Glama

set_diet_plan_template_marketplace

List or unlist a diet 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_diet_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

A3.6/5.0
Behavior4/5

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

Annotations already declare it as a non-read, non-destructive, non-open-world mutation. The description correctly adds context: the operation is confirm-gated and does not process payment. It omits permission requirements and the effect of unlisting on an existing price, which keeps it below 5.

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 sentences, front-loaded with the action and scope, followed by the payment clarification. No redundant repetition of tool name or title, though the payment caveat could be shorter.

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 mutation tool with 5 parameters, no output schema, and only 20% schema coverage, the definition covers purpose and the confirm gate but leaves gaps: permission requirements, currency semantics, and price behavior on unlisting. It is adequate but not complete.

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?

Only 1 of 5 parameters has schema description (20% coverage), so the description must compensate. It implies that isMarketplace toggles listing and that price is set, which helps map two parameters. It says nothing about currency format, whether price is required when listing, or what units price uses.

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 opens with a specific verb pair and resource: 'List or unlist a diet plan template on the Trainzilla marketplace, and set its price.' This distinguishes it from set_workout_plan_template_marketplace (different resource) and set_diet_plan_marketplace (plan, not template). It does not explicitly name a sibling or contrast with it, so it stops short of a 5.

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 confirm gate is described clearly ('confirm-gated'), and the description states what the tool does not do ('does not process any payment'). However, there is no guidance on when to list versus unlist, or on prerequisites such as ownership of the template. Usage is implied by the purpose sentence rather than stated.

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.