Skip to main content
Glama
Sign In
Wellness Nourish

Wellness Nourish

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List personal nutrition memory

nourish_list_memory
Read-onlyIdempotent

Retrieve locally stored meals and nutrition preferences to power personal Telegram shortcuts. Get structured or summary views for quick recall.

Instructions

Read local remembered meals and nutrition preferences for personal Telegram shortcuts.

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": "nourish_list_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. Addedv0.7.2
  2. Removedv0.7.0
  3. 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 and destructiveHint=false. Description adds context about local storage and Telegram, consistent with safe read behavior.

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 front-loads the core purpose with no wasted words.

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?

Adequate for a simple read tool with strong annotations, but lacks mention of return format or pagination, which would be helpful given no output schema.

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?

Two parameters (privacy_mode, response_format) with 50% schema coverage; only privacy_mode has a schema description. Tool description adds no parameter information, failing to compensate for the lack of response_format description.

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 clearly states verb 'Read' and resource 'local remembered meals and nutrition preferences', with context of 'personal Telegram shortcuts'. It distinguishes from sibling tools like nourish_list_intake and nourish_remember_meal.

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 guidance on when to use vs alternatives. Context implies it's for retrieving stored memories, but no when-not or alternative references.

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