Skip to main content
Glama

dietbox_prescription_get

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: get]

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": {
      "prescription_id": "<prescription_id>"
    },
    "name": "dietbox_prescription_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
takeNo
searchNo
accountNo
patient_idNo
patient_idsNo
prescription_idYes
prescription_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / prescription_id / default
      Removed value: -""
    • removedInput schema / properties / prescription_ids / items / default
      Removed value: -""
    • addedInput schema / required
      Added value: +[
      +  "prescription_id"
      +]
  2. 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 the full safety profile (readOnly, idempotent, non-destructive, closed world), so the bar is lower. The description adds one genuinely useful trait, bulk/batched execution via patient_ids and prescription_ids, but says nothing about pagination behaviour, result ordering, or what happens when only some ids resolve, and the '[Flattened action]' marker is unexplained context rather than disclosure.

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

Conciseness3/5

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

The opening sentence plus exclusion is well front-loaded and wastes nothing. The follow-on action enumeration and the bracketed '[Flattened action: get]' artifact add length without resolving the get-vs-list ambiguity, and the bulk sentence is tacked on rather than integrated.

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 read-only tool with strong safety annotations and no output schema, the definition covers identity, the key sibling exclusion, the id requirement, and bulk semantics. Gaps remain: no account scoping explanation and no pagination defaults (skip/take/search) despite 0% schema coverage, but nothing critical blocks a correct call.

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 must carry the load. It does map patient_id to list, prescription_id to detail, and the plural forms to bulk execution, but skip, take, search, and account are entirely undocumented anywhere, leaving half the parameters semantically opaque.

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 ('Read supplement/herbal medicine prescriptions') and explicitly distinguishes it from the food-plan sibling dietbox_meal_plan. However, the name says 'get' while the description advertises three modes (list, get, list_models) and notes '[Flattened action: get]', which muddies what this particular tool call actually does relative to dietbox_prescription_list and dietbox_prescription_list_models.

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?

The exclusion is explicit and valuable: NOT meal plans, use dietbox_meal_plan for food plans. But no guidance is given on when to choose this tool over the sibling dietbox_prescription_list or dietbox_prescription_list_models, even though the description claims list behaviour and the schema requires prescription_id, leaving the agent to infer the boundary.

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.