Skip to main content
Glama
googlarz

Suunto MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_recovery

Fetches recovery and HRV time-series samples for a specified date, providing recovery balance and stress state per sample. Empty response if no data is available.

Instructions

Returns recovery and HRV time-series samples from the /247samples API for one calendar day. Each sample: { timestamp (ISO8601), Balance (0.0–1.0 recovery balance), StressState (0=Invalid, 1=Relaxing, 2=Active, 3=Passive, 4=Stressful) }. Days without recovery data return an empty payload. Use list_recovery for a date range. Requires Recovery API subscription on apizone; returns 404 without it. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesCalendar date YYYY-MM-DD. Suunto syncs once daily, so today's data is usually incomplete — but the API responds 200 with an empty or partial payload for today/future dates, it does not throw SuuntoNotFoundError (confirmed live). Use yesterday or earlier for complete results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.4
    • changedInput schema / properties / date / description
      Previous value: -"Calendar date YYYY-MM-DD. Suunto syncs once daily — today or future dates typically return SuuntoNotFoundError; use yesterday or earlier for reliable results."New value: +"Calendar date YYYY-MM-DD. Suunto syncs once daily, so today's data is usually incomplete — but the API responds 200 with an empty or partial payload for today/future dates, it does not throw SuuntoNotFoundError (confirmed live). Use yesterday or earlier for complete results."
  2. Changed1 schema field changedv0.9.2
    • changedInput schema / properties / date / description
      Previous value: -"Calendar date YYYY-MM-DD. Example: 2026-04-20."New value: +"Calendar date YYYY-MM-DD. Suunto syncs once daily — today or future dates typically return SuuntoNotFoundError; use yesterday or earlier for reliable results."
  3. Changed3 schema fields changedv0.9.1
    • addedInput schema / properties / date / examples
      Added value: +[
+  "2026-04-20"
+]
    • addedInput schema / properties / date / maxLength
      Added value: +10
    • addedInput schema / properties / date / minLength
      Added value: +10
  4. Changed3 schema fields changedv0.9.0
    • changedInput schema / properties / date / description
      Previous value: -"YYYY-MM-DD"New value: +"Calendar date YYYY-MM-DD. Example: 2026-04-20."
    • addedInput schema / properties / date / format
      Added value: +"date"
    • addedInput schema / properties / date / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
  5. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries full behavioral disclosure. It reveals the 404-without-subscription behavior, empty payloads for days without data, the read-only nature, and the exact sample fields and enum meanings, going well beyond a minimal statement.

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?

Every sentence earns its place: purpose, output format, empty behavior, alternative tool, subscription requirement, and read-only status. The description is compact, front-loaded with the main action, and contains no repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only tool with a detailed input schema, the description provides all necessary behavioral context: what is returned, what an empty payload means, what happens without a subscription, and where to go for a date range. Nothing essential is missing.

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%, and the schema already thoroughly documents the date parameter including format, examples, and the useful caveat about today's incomplete data. The tool description adds scope context ('one calendar day') but does not materially improve parameter meaning beyond the schema.

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?

States a specific verb and resource ('Returns recovery and HRV time-series samples from the /247samples API') and clearly scopes it to one calendar day. The output sample structure is described, and it is distinguishable from the sibling list_recovery by its single-day scope.

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

Usage Guidelines5/5

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

Explicitly names list_recovery as the alternative for date-range queries, making the single-day use case clear. It also states the subscription requirement and the empty-payload behavior, giving agents concrete conditions for when this tool is appropriate.

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