Skip to main content
Glama

dietbox_chat_list

Read-onlyIdempotent

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

[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_chat_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
takeNo
unreadNo
accountNo
patient_idNo
patient_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely new behavioral context with the bulk/batched execution note, but omits return shape, ordering, and how 'take' bounds the result set.

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 text is short and front-loaded, which is good, but the 'Actions: list ..., messages ...' enumeration describes an action that is not part of this flattened tool, spending characters on misleading information rather than on the parameters that actually need explanation.

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 a five-parameter read tool with no output schema and no parameter descriptions, the definition is only minimally sufficient. It never states what a returned conversation contains, whether results are paginated by 'take', or how account scoping interacts with the filters.

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%, so the description must carry the parameter burden. It explains patient_id (patient filter), unread (unread filter) and patient_ids (batch input), but leaves 'take' (pagination/limit) and 'account' completely unexplained 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 opens with a specific verb and resource: 'Read chat conversations in Dietbox', and adds filters (patient/unread) plus bulk behavior. It is somewhat muddied by also advertising a 'messages' action that is now a separate sibling tool (dietbox_chat_messages), which could make an agent believe message history is retrievable here.

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?

It implies usage through the listed filters and notes that patient_ids enables batched execution, but it never says when to pick this over dietbox_chat_messages or dietbox_chat_write, nor any prerequisites such as authentication or account scoping.

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.