Skip to main content
Glama

compare_whoop_periods

Read-onlyIdempotent

Compare two bounded WHOOP periods to surface counts and missing values, so you can assess differences without making causal claims.

Instructions

Compare two bounded periods; disclose counts and missingness. No causal claims.

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": {
      "kind": "<kind>",
      "first_start": "<first_start>",
      "first_end": "<first_end>",
      "second_start": "<second_start>",
      "second_end": "<second_end>"
    },
    "name": "compare_whoop_periods"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
first_endYes
second_endYes
first_startYes
second_startYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, open-world and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: results disclose counts and missingness, and the tool refrains from causal interpretation. It does not say what happens when a period is empty or how large the periods may be, which matters for an open-world tool.

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 compact clauses with the operation front-loaded and no filler. The brevity is efficient, though it edges toward under-specification given five undocumented parameters.

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

Completeness2/5

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

Five required parameters at 0% schema coverage with no output schema means the description carries the full burden, and it leaves the single most important field ('kind') undefined. For a comparison tool whose correctness depends on choosing a valid kind and well-formed date bounds, this is a significant gap.

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?

Schema description coverage is 0% across five required parameters, each carrying only a bare title like 'Kind', 'First Start'. The description compensates minimally by implying the first_/second_ pairs delimit two bounded ranges, but it never states accepted 'kind' values (no enum exists) or the expected date/time format, so an agent could easily call it with invalid arguments.

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

Purpose3/5

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

The description names a specific verb ('Compare') and scope ('two bounded periods'), so the general operation is identifiable. However, it never says what is being compared (recovery? sleep? workouts?) or that the 'kind' parameter selects that dimension, leaving the actual object of comparison vague. It also does not distinguish itself from the sibling summarize_whoop_period, which plausibly covers similar ground.

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?

'No causal claims' is an output/interpretation constraint, not guidance on when to call this tool. There is no statement of when to prefer it over summarize_whoop_period or the list_* siblings, and no mention of prerequisites such as both periods being bounded or non-overlapping.

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