Skip to main content
Glama
Sign In
Trainbud

Trainbud

by Zsadigzade
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_sleep_data

Retrieve sleep duration, quality score, stage breakdown, and interruptions from recent nights to analyze sleep patterns.

Instructions

Returns sleep duration, quality score, stage breakdown, and interruptions for recent nights.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_sleep_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
nightsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.2

TDQS

B3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It does convey that the tool returns data for 'recent nights' and implies a read-only operation, but it fails to explain default behavior, how far back 'recent' reaches, or whether the 'nights' parameter controls the time window.

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?

The description is a single, front-loaded sentence that lists concrete output components, which is efficient and easy to parse. However, the brevity comes at the cost of missing crucial parameter and usage details.

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?

The tool has one optional parameter, no output schema, and no annotations, so the description must supply essential context. It lists return fields but leaves the meaning of 'nights' and the default behavior unspecified, making correct invocation uncertain when a specific night count is requested.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not explain the meaning or effect of the 'nights' parameter. The phrase 'recent nights' hints at a time window but never links it to the parameter, leaving the agent unable to determine how to request a specific number of nights.

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?

The description uses a specific verb 'Returns' and a precise resource: sleep duration, quality score, stage breakdown, and interruptions. It clearly distinguishes this tool from sibling tools focused on heart rate, stress, recovery, and other non-sleep metrics.

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?

The description provides no guidance on when to choose this tool over siblings like get_recovery_status or get_week_review, nor does it mention any exclusions or prerequisites. Usage must be inferred entirely from the tool name and output list.

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