Skip to main content
Glama

dietbox_patient_list

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

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

Input Schema

NameRequiredDescriptionDefault
skipNo
takeNo
orderNo
searchNo
accountNo
is_activeNo
patient_idNo
patient_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the description earns credit for adding non-obvious context: the account gets temporarily blocked for "atividade automatizada" on rapid repeated calls, and the tool reports a wait time after a block. It does not explain pagination totals or the shape of the returned patient records.

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 rate-limit rule is front-loaded and worth its space, but the definition carries noise: the flattened-action artifact, a language switch mid-description, and a "get" action that is not part of this tool. Structure is workable but not tight.

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 an 8-parameter read tool with no output schema, the description covers the critical operational risks (batching, blocking, backoff) and the main modes of use. It stops short of describing return fields or the meaning of account/is_active/order, which an agent must infer from the schema names alone.

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 compensate. It does explain search (by name), pagination (list with larger take, e.g. 200), patient_id for get, and patient_ids for bulk, but leaves account, is_active, skip, and order completely undefined in both places.

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 patients in Dietbox") and enumerates the operations, but it also advertises a "get" action that belongs to the separate sibling dietbox_patient_get, and the "[Flattened action: list]" marker reveals only list is actually exposed. That internal tension keeps it from a 5, but an agent can still tell this is the patient read/list tool.

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 usage rule for bulk retrieval — one list call with a large take rather than one name search per patient — and warns against retrying during a temporary block. What's missing is routing guidance versus the close siblings dietbox_patient_get and dietbox_patient_write_*, which the description never names.

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.