Skip to main content
Glama

Get Sleep Training Correlation

get_sleep_training_correlation

Calculate how lifting volume relates to sleep across a date range, returning sample size, correlation coefficient, lag, and period.

Instructions

Correlation between lifting volume and sleep, with n, r, lag and period.

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_sleep_training_correlation"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYesDate as YYYY-MM-DD
lag_daysNo0 = same day; 1 = training day vs the next night
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.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden and does very little: it does not state that this is a read-only computation, what happens when the sample is tiny or data is missing, or how the date range bounds the analysis. Listing 'n, r, lag and period' gestures at output shape, but an output schema already exists, so it adds little behavioral substance.

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

Conciseness3/5

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

It is very short and front-loaded, but it is a sentence fragment rather than a structured statement, and the brevity crosses into under-specification. No wording is wasted, yet the space saved is not repurposed into anything an agent needs.

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 need not enumerate return fields, and the parameter schema is fully documented. What remains missing is the interpretive context an agent needs to use the result well (direction of correlation, minimum sample considerations) and any annotation substitute, which for an unannotated analysis tool is a real 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 description coverage is 100% and the lag_days semantics (0 = same day, 1 = training day vs next night) are documented in the schema itself. The description's mention of 'lag' merely echoes the schema, adding no new meaning for start_date, end_date, or the 0-7 bounds.

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 fragment names a specific analysis (correlation between lifting volume and sleep), which is more informative than a restatement of the name, but it has no verb and gives no sense of what is returned versus what is required. It does nothing to distinguish it from analysis-oriented siblings like get_lifting_trend or get_overview.

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 guidance on when to call this tool, no prerequisites (e.g. whether sleep and lifting data must both exist for the range), and no mention of alternatives among the many get_* siblings. An agent must infer usage entirely from the name.

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