Wellness Project MCP

show_week_sleep

Read-onlyIdempotent

Displays your past 7 days of sleep hours and sleep score in an inline chart, with a brief text summary.

Instructions

Show the user their past 7 days of sleep (hours per night and sleep score) as an inline chart. When the user asks about this, prefer calling this tool and rendering the interactive MCP app over describing the underlying rows in text. Returns a short text summary alongside the visual view.

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

Input Schema

Name	Required	Description	Default
`range`	No	Time window. One of 7d, 30d, 90d, 1y. Default 7d.

Output Schema

Name	Required	Description	Default
`kind`	Yes	Widget discriminant identifying the payload shape.
`generatedAt`	No	ISO timestamp the snapshot was built.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Sep 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false; the description adds value beyond that by disclosing that the tool renders an interactive MCP app and 'returns a short text summary alongside the visual view.' This informs the agent how to present the invocation result, which annotations cannot convey.

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?

Three sentences, each earning its place: core function and format, tool-selection guidance, and return behavior. The content is front-loaded with the primary purpose and contains no redundant phrasing.

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?

For a single-optional-parameter tool with a fully documented schema, output schema, and safety annotations, the description covers what to invoke, when to prefer it, and what to expect back. Minor gaps are reconciling the '7 days' wording with the larger range windows and explicitly naming show_sleep_detail as the drill-down alternative.

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 coverage is 100% — the range parameter is fully described with its enum values and default ('Default 7d'), so the schema carries the burden. The description adds no parameter detail and even centers on 'past 7 days' while the schema permits 30d/90d/1y; at full coverage this lands at the baseline 3.

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 states a specific verb and resource — 'Show the user their past 7 days of sleep (hours per night and sleep score) as an inline chart' — naming both content and output format. It also differentiates from sibling list tools by preferring 'rendering the interactive MCP app over describing the underlying rows in text.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear selection context: 'When the user asks about this, prefer calling this tool... over describing the underlying rows in text,' which routes the agent away from the list_sleep pattern. It stops short of naming explicit alternatives or exclusions, such as when to send the user to show_sleep_detail for granular detail.

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

Deploy Server