Skip to main content
Glama
davidmosiah

Wellness Nourish

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Weekly summary

nourish_weekly_summary
Read-onlyIdempotent

Summarize a week of nutrition intake totals from any start date, with options for summary, structured, or raw privacy levels and JSON or Markdown output.

Instructions

Summarize seven days of local intake totals from a start date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_dateNo
privacy_modeNosummary = high-level totals without item detail; structured = default full JSON-friendly fields; raw = same as structured for this local store (parity).structured
response_formatNojson

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.2
    • addedInput schema / properties / privacy_mode
      Added value: +{
+  "default": "structured",
+  "description": "summary = high-level totals without item detail; structured = default full JSON-friendly fields; raw = same as structured for this local store (parity).",
+  "enum": [
+    "summary",
+    "structured",
+    "raw"
+  ],
+  "type": "string"
+}
  2. First observedv0.6.6

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds behavioral context by specifying the time window (seven days) and the data scope (local intake), which goes beyond just summarizing totals. No contradictions with 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?

The description is a single, concise sentence with no waste. It conveys the essential purpose without extraneous detail, fitting the brevity ideal.

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?

Without an output schema, the description omits details on return format, pagination, or error handling. The scope 'local intake totals' is clear but the agent lacks full context on what the summary includes (e.g., macronutrients, items). Adequate for a simple tool but not complete.

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 low at 33%, with only privacy_mode having a description. The tool description mentions 'start date' but does not clarify format, default, or behavior. The description fails to compensate for the poorly documented parameters.

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?

The description specifies the verb 'summarize', the resource 'local intake totals', and the scope 'seven days from a start date'. This clearly distinguishes it from siblings like nourish_daily_summary (one day) or nourish_hydration_summary (water).

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?

The description does not provide any guidance on when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it. The purpose is clear but usage contexts are left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools