Skip to main content
Glama

dietbox_prescription_list

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]

Bulk support: accepts patient_ids, prescription_ids for batched execution.

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": {
      "patient_id": "<patient_id>"
    },
    "name": "dietbox_prescription_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
takeNo
searchNo
accountNo
patient_idYes
patient_idsNo
prescription_idNo
prescription_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[
      +  "patient_id"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds real value by disclosing bulk execution support via patient_ids and prescription_ids. It does not describe pagination behavior, default limits, or what a batched call returns, which keeps it from a 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?

The key disambiguation is front-loaded in the first clause and the whole definition is three short lines with no filler. The bracketed flattening note and the inline action list add slight noise for a tool that is currently only the list action.

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 tool with no output schema and no parameter descriptions, the definition should at least explain the pagination/filter parameters and whether batched calls return a merged or per-patient structure. It covers domain scoping and bulk mode well but leaves the agent guessing on paging and result shape.

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 0% across 8 parameters, so the description carries the full burden and only partially does so: patient_id, prescription_id, patient_ids, and prescription_ids get meaning, but skip, take, search, and account are left completely unexplained. Half the parameters remain undocumented in both schema and description.

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 verb and resource ("Read supplement/herbal medicine prescriptions") and explicitly excludes the nearest confusable domain ("NOT meal plans — use dietbox_meal_plan"). It loses a point because it enumerates list/get/list_models as if they were actions of this tool, while dietbox_prescription_get and dietbox_prescription_list_models exist as separate siblings; only the bracketed "[Flattened action: list]" rescues the agent from that ambiguity.

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?

It gives an explicit use condition (reading supplement/herbal prescriptions) and an explicit exclusion with the alternative to use instead (meal plans → dietbox_meal_plan). It does not explicitly say when to prefer this over the sibling dietbox_prescription_get or dietbox_prescription_list_models, though the action breakdown implies the routing.

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.