Skip to main content
Glama

dietbox_prescription_list_models

Read-onlyIdempotent

Read supplement/herbal medicine prescriptions in Dietbox (NOT meal plans — use dietbox_meal_plan for food plans). Actions: list (by patient_id), get (full detail by prescription_id), list_models (reusable templates).

[Flattened action: list_models]

Bulk support: accepts patient_ids, prescription_ids for batched execution.

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": "dietbox_prescription_list_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
takeNo
searchNo
accountNo
patient_idNo
patient_idsNo
prescription_idNo
prescription_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds genuine value by disclosing bulk execution via patient_ids/prescription_ids, but it does not explain the template return shape, whether pagination applies, or how 'search' behaves, and the enumeration of list/get actions that this flattened tool cannot perform can mislead.

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 short, front-loaded sentences with the scope exclusion placed first and no filler. The action list is somewhat vestigial for a flattened tool but costs little space.

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 and 8 undocumented parameters, the agent still lacks pagination behavior and a description of what a 'model' template contains. The safety profile and bulk semantics are adequately conveyed, so the definition is usable but has clear informational gaps for a template-listing tool.

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?

Schema description coverage is 0% across 8 parameters, so the description carries the full burden. It explains only patient_id, prescription_id, patient_ids and prescription_ids; skip, take, search and account are never mentioned, even though search and take are the most relevant controls for listing reusable templates.

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 names a specific resource (supplement/herbal medicine prescriptions) and explicitly excludes the adjacent one (meal plans -> dietbox_meal_plan), which an agent needs to avoid a wrong call. It is slightly muddied because it enumerates three actions (list/get/list_models) while the tool is flattened to list_models, so the agent must read the '[Flattened action: list_models]' marker to know what this invocation actually does.

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?

There is one strong, explicit routing rule: not meal plans, use dietbox_meal_plan instead. However, the schema includes sibling prescription tools (dietbox_prescription_list, dietbox_prescription_get) and the description never says why an agent would pick list_models (reusable templates) over those, nor when a template listing is appropriate versus a per-patient listing.

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.