Skip to main content
Glama

get_lifestyle_logging_data

Read-only

Fetch lifestyle logging data for a specific date to track behaviors and evaluate their impact on health metrics.

Instructions

Get lifestyle logging data for a specific date

    Returns lifestyle logging data which allows users to track behaviors
    and their impact on health metrics.

    Args:
        date: Date in YYYY-MM-DD format
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>"
    },
    "name": "get_lifestyle_logging_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that results let users track behaviors against health metrics, but says nothing about data volume, missing-data behavior for dates with no entries, or response shape — which matters since openWorldHint suggests externally sourced data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences plus an Args block — front-loaded with the action and efficiently ordered. The Args section is slightly redundant given the single obvious parameter, but it is where the format detail lives, so it earns its place.

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?

For a one-parameter read tool with annotations covering safety, the essentials are present, but with no output schema the description should say what 'lifestyle logging data' actually contains (fields, granularity, empty-date behavior). That undefined return content is the main completeness gap.

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 0% (the schema only labels the field 'Date'), and the description compensates by specifying the YYYY-MM-DD format, which is genuinely useful. It does not, however, address timezone handling, date boundaries, or whether future dates are valid, so the single parameter is only partially clarified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (Get) and resource (lifestyle logging data) scoped to a date, and the second sentence clarifies that the payload is behavior-tracking data tied to health metrics. That distinguishes it reasonably well from sibling metric tools like get_steps_data or get_sleep_data, though it never states which behaviors or metrics are covered.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no reference to alternatives such as the other per-date metric tools in the sibling set. The only usage signal is the implicit notion that it is date-scoped, leaving the agent to guess when this is the right call over a related data tool.

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