Skip to main content
Glama

sleep_analysis

Analyze how prior-day training, calories, and meal timing affect sleep quality. Correlate sleep scores with training intensity, total calories, and meal timing.

Instructions

Analyze what affects sleep quality — prior-day training, calories, timing.

Correlates sleep scores with training intensity, total calories, and meal
timing from the preceding day.

Args:
    start_date: Start date (YYYY-MM-DD). Default: 30 days ago.
    end_date: End date (YYYY-MM-DD). Default: today.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateNo
start_dateNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided; description carries full burden. It only states analysis and correlation, but does not disclose side effects, authorization needs, or rate limits. Assumed read-only but not confirmed.

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?

Very concise: two sentences for purpose and two lines for parameters. Front-loaded key information with no wasted words.

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

Completeness4/5

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

For a simple analysis tool with 2 parameters and an output schema, the description is adequate. It explains purpose and parameters, though could mention prerequisites like data availability.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (no descriptions), but description adds meaningful context: date format (YYYY-MM-DD) and defaults (30 days ago, today). Compensates for schema gap.

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?

Description clearly states 'Analyze what affects sleep quality' with specific correlations to training, calories, and timing. It distinguishes from siblings by focusing on sleep, unlike other tools like recovery_check or nutrition_performance_correlation.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool vs alternatives. Purpose is implied but no exclusions or alternatives mentioned, leaving the agent to infer.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NasserAlbusaidi/macrofactor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server