show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
DietBox
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds that it shows 'MCP platform and adapter versions', providing specific output context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence with no wasted words. Perfectly concise for the tool's simplicity.
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?
Given low complexity, rich annotations, and no parameters, the description is adequate. It tells what the tool returns, though output format is absent. Slightly more detail about the return structure could improve completeness.
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 has zero parameters with 100% coverage, so baseline is 3. No parameter information is needed, and description adds nothing beyond what schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses specific verb 'Show' and identifies the resource as 'MCP platform and adapter versions'. It clearly distinguishes from sibling tools which are about authentication, patient management, and other distinct functionalities.
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?
No explicit when-to-use or alternative guidance is provided. The purpose is self-evident, but the description does not clarify when not to use it or suggest alternatives, leaving usage implied.
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.
TDQS
B3/5.0
Disambiguation2/5
Many tools have nearly identical descriptions, differing only by a single action name (e.g., dietbox_agenda_list vs dietbox_agenda_summary, multiple anamnesis read tools). This makes it hard for an agent to choose the correct tool. The splitting of CRUD operations into separate tools per action creates significant overlap.
Naming Consistency3/5
Most Dietbox tools follow a consistent `dietbox_<entity>_<action>` snake_case pattern, but tools like `authenticate`, `connect`, `marketplace`, `report_bug`, `show_version`, and `toolkit_info` break this, making naming partially inconsistent. Overall, the pattern is clear for the core domain.
Tool Count2/5
With 42 tools, the server is overburdened. Many tools are redundant due to splitting actions (e.g., three read tools for anamnesis), and non-domain tools (marketplace, bug reporting) inflate the count unnecessarily. A more streamlined set of 15-20 tools would be more appropriate.
Completeness3/5
The server covers a wide range of nutrition practice features: patients, appointments, anamnesis, anthropometry, chat, food diary, goals, finances, meal plans (read-only), prescriptions, and clinical records. However, notable write operations are missing (meal plans, goals, finance transactions), and some read-only tools lack corresponding edits.