Skip to main content
Glama

create_diet_plan_template

Save a reusable diet plan template (confirm-gated). meals follow the same shape as create_diet_plan's — every meal must include a non-empty ingredients array with quantities.

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": {
      "title": "<title>",
      "visibility": "<visibility>",
      "meals": "<meals>"
    },
    "name": "create_diet_plan_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNo
tagsNo
mealsYes
titleYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
difficultyNo
visibilityYes
descriptionNo

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 readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds a real behavioral constraint — meals must have a non-empty ingredients array with quantities — but the '(confirm-gated)' note merely restates what the confirm parameter already documents in the schema.

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 short sentences, front-loaded with the action and the gating behavior, with no filler. The reference to 'the same shape as create_diet_plan's' forces the agent to consult another tool, slightly reducing efficiency.

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 an 8-parameter mutation tool with no output schema and thin annotation coverage, the description covers the two most ambiguous inputs but omits the visibility/goal/difficulty semantics and says nothing about what is returned or side effects on existing templates. Adequate but with visible 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 description coverage is only 13% across 8 parameters, so the description carries real weight; it does explain the two hardest items, the confirm gate and the free-form meals array shape. However, title, visibility, goal, tags, difficulty, and description are left entirely to the enum/schema, so compensation is partial.

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?

States a specific verb and resource: save a reusable diet plan template. The word 'reusable' implicitly distinguishes templates from create_diet_plan, and the description cross-references create_diet_plan for meal shape, so an agent can roughly tell them apart — though it never explicitly says 'use this instead of create_diet_plan when you want a reusable blueprint.'

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?

Mentions the confirm gate, which tells the agent a two-step preview/execute flow exists, but gives no explicit when-to-use versus create_diet_plan, update_diet_plan_template, or list/get siblings. Usage is only implied by the word 'reusable.'

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.