Fetches essential startup information about the Mealie app, such as configuration and readiness details, to aid in initialization and troubleshooting.
Get Startup Info [GET /api/app/about/startup-info] returns helpful startup information
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description only states that it 'returns helpful startup information' without disclosing any behavioral traits such as read-only nature, authentication requirements, or side effects. Since annotations are absent, the description carries the full burden and falls short.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very brief, but it includes the endpoint and a vague return statement. It is not overly verbose, but the opening 'Get Startup Info' is redundant with the tool name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description should clarify what 'startup information' includes (e.g., version, configuration). The current description is too vague to fully inform an agent about the tool's output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has no parameters, and schema coverage is 100%, so no parameter documentation is needed. The description does not contribute additional meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and the resource 'Startup Info', and mentions it returns helpful information. However, it does not differentiate from the sibling tool 'app_about_get_app_info', which likely overlaps in purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like 'app_about_get_app_info'. It does not specify any prerequisites or context for use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.