Skip to main content
Glama

list_diet_plan_templates

Read-only

List the coach's diet plan templates (id, title, tags, difficulty, goal).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_diet_plan_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
searchNo
onlyMineNo
pageSizeNo
pageNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful scope ('the coach's') and the per-item fields, but omits pagination behavior despite pageSize defaulting to 50 with a 100 maximum, which an agent should know.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with the resource stated first and the output fields front-loaded; there is no wasted wording whatsoever.

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?

With no output schema, enumerating the returned fields is genuinely helpful. However, for a tool with five undocumented optional parameters and unpaginated-by-default listing, the definition is too thin to be complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All five parameters (tag, search, onlyMine, pageSize, pageNumber) have 0% schema description coverage, so the description carries the full burden of explaining them and explains none. The parenthetical field list describes results, not the tag/search/onlyMine filtering semantics an agent would need to filter correctly.

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?

Specific verb ('List') plus resource ('diet plan templates'), with the returned fields enumerated in parentheses so the agent knows the shape of each item. It does not explicitly distinguish itself from the adjacent list_diet_plans sibling, which lists plans rather than templates, so a 4 rather than 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says when to pick templates over diet plans, when to use onlyMine, or what preconditions exist. The name implies a browsing operation, but the agent is left to infer any routing between this and the many sibling list_* tools.

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.