Skip to main content
Glama

dietbox_patient_get

Read-onlyIdempotent

Read patients in Dietbox. Actions: list (paginated, search by name), get (full detail, requires patient_id).

Para localizar VÁRIOS pacientes, faça UMA chamada list com take maior (ex.: 200) e filtre o resultado, em vez de uma busca por nome para cada paciente: o DietBox bloqueia a conta temporariamente ("atividade automatizada") quando recebe muitas chamadas seguidas. Se o bloqueio acontecer, a ferramenta avisa quanto tempo esperar; não repita a chamada antes disso.

[Flattened action: get]

Bulk support: accepts patient_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_patient_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
takeNo
orderNo
searchNo
accountNo
is_activeNo
patient_idYes
patient_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.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description correctly focuses on what they cannot express: provider-side rate limiting that can temporarily block the whole account, and the fact that the tool itself reports the wait time. The bulk-execution note adds further behavioral context. Missing pagination behavior and ordering semantics keeps it off 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.

Conciseness3/5

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

The core is front-loaded and the rate-limit warning earns its length. However, the text abruptly switches from English to Portuguese mid-description, which fragments readability, and includes scaffolding artifacts ('[Flattened action: get]', 'Bulk support:') that read as generator output rather than authored guidance.

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

Completeness2/5

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

The schema marks patient_id as required while the description describes a list action that would not use it, and the tool is flattened to `get` only — an agent cannot tell whether passing take/search without patient_id is valid or will fail validation. With no output schema, the description's 'full detail' claim is the only signal about what comes back. The unresolved get/list/required-parameter contradiction is a substantive omission for a definition this complex.

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 has to carry the load. It does explain patient_id (required, one patient's full detail), take/search (list paging and name filtering), and patient_ids (bulk batching), which is meaningful added meaning. But skip, order, account, and is_active are left completely undefined 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 concrete resource (patients in Dietbox) and splits it into two explicit actions with distinct semantics: list (paginated, search by name) and get (full detail, requires patient_id). That is enough for an agent to tell read-patient-detail apart from a write or delete. It loses a point because it advertises a list action on a tool named and flattened to `get`, while a sibling `dietbox_patient_list` exists and is never mentioned, leaving a real routing 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 genuinely actionable when-to guidance: to locate several patients, make ONE list call with a large take (e.g. 200) and filter locally rather than issuing one name search per patient. It also names the failure condition (temporary account block for 'automated activity') and says not to retry before the stated wait. It stops short of 5 because it never tells the agent when to pick this tool over the sibling `dietbox_patient_list`.

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.