Skip to main content
Glama

list_diet_plans

Read-only

List a client's diet plans (id, title, dates, and the PDF it came from if any). Pass the client's user _id. This does NOT include the meals — call get_diet_plan with a plan _id to read them.

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": {
      "clientId": "<clientId>"
    },
    "name": "list_diet_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 the safety profile is covered. The description adds real value by disclosing the returned fields and the explicit exclusion of meal data, but says nothing about ordering, pagination, or what an empty/unassigned client returns.

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?

Three short sentences, front-loaded with what is returned, then the required argument, then the boundary and the alternative. Nothing is redundant and nothing is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only list tool with no output schema, the definition covers purpose, the key argument's meaning, and the main misuse risk (expecting meals). Pagination or result-size behavior would be the only remaining gap, and that is minor here.

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

Parameters4/5

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

With 0% schema description coverage, the description carries the burden and does add meaning: the single parameter is the client's user _id rather than an internal client record id, which is a distinction the bare 'clientId: string' schema does not convey. It still leaves the id format (e.g. '_id' as a Mongo-style id) implicit.

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 specific verb (list) and resource (a client's diet plans), then enumerates the returned fields (id, title, dates, source PDF) so the agent knows exactly what shape of data this yields. It also explicitly separates itself from get_diet_plan, which is the sibling an agent might otherwise confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear routing guidance: this tool excludes meals, and get_diet_plan with a plan _id is named as the alternative for reading them. It also tells the caller what to pass. It does not address how this relates to the other list variants (list_my_plans, list_organization_plans), but the 'a client's' framing already scopes the use case.

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.