Skip to main content
Glama

dietbox_chat_messages

Read-onlyIdempotent

Read chat conversations in Dietbox. Actions: list (conversations, filter by patient/unread), messages (message history for patient_id).

[Flattened action: messages]

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_chat_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
takeNo
unreadNo
accountNo
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

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description's only added behavior is bulk execution via patient_ids, which is genuinely useful context, but it says nothing about pagination (the take default of 50) or what the returned message history looks like.

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?

Short and front-loaded, but the 'Actions: list (conversations...)' sentence describes an action the flattened tool does not expose, so a chunk of the text is misleading rather than load-bearing.

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?

With 5 undocumented parameters, no output schema, and an action-flattening note, the description does not give enough for reliable invocation — notably silent on 'take' and 'account' and on how the required patient_id interacts with the optional patient_ids bulk path.

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 5 parameters, so the description must compensate. It explains patient_id (message history) and patient_ids (bulk batching) but leaves 'take' and 'account' entirely unexplained, and 'unread' only implicitly via the list action that is not actually available.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read chat conversations in Dietbox') and marks the flattened action as 'messages'. However, it also advertises a 'list' action that the tool, as flattened, does not expose, and a sibling named dietbox_chat_list exists — leaving the agent uncertain whether this tool lists conversations or reads a patient's message history.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives hints of usage ('filter by patient/unread', bulk via patient_ids) but never says when to pick this over dietbox_chat_list or dietbox_chat_write, and the advertised 'list' action conflicts with the flattened-to-messages note.

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.