Skip to main content
Glama

Get Overview

get_overview

Review a consolidated health overview across weight, sleep, activity, recovery, workouts, lifting, and consistency for a specified date range.

Instructions

One-call overview: weight, sleep, activity, recovery, workouts, lifting, consistency.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYesDate as YYYY-MM-DD
start_dateYesDate as YYYY-MM-DD

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and supplies almost none: it does not state that the tool is read-only, whether date ranges are inclusive, how much data a range can span, or whether responses are cached or rate-limited. Listing the domains returned is the only behavioral content, and it partly duplicates what the output schema already conveys.

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?

A single front-loaded fragment that spends no words on preamble, and 'One-call overview' leads with the key differentiator. The domain list is dense but earns its place by telling the agent what comes back; it is slightly list-like at the cost of prose clarity.

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?

Because an output schema exists, the description is not obliged to explain return values, and the date parameters are fully covered by the schema. What remains missing is the guidance layer an agent needs with eight siblings present: no statement of when this omnibus call beats get_daily_checkin or the lifting-specific tools, and no behavioral notes to substitute for absent annotations.

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 description coverage is 100%, so both start_date and end_date are already documented with format and pattern; the baseline is therefore 3. The description adds nothing about date semantics, such as whether the range is inclusive or how it interacts with the per-domain metrics, so it neither compensates nor detracts.

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?

The description names a specific resource set (weight, sleep, activity, recovery, workouts, lifting, consistency) and frames the tool as a combined 'one-call overview', which implies aggregation across domains rather than a single-metric tool like its siblings. It stops short of explicitly contrasting itself with get_daily_checkin or get_lifting_summary, so an agent must infer the distinction.

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 explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative. The phrase 'One-call overview' weakly implies a use case (pull a broad cross-domain snapshot instead of several narrow calls), but that is inference rather than guidance.

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