WhenPeak

whenpeak_performance_now

Report the current moment's performance state for the account this server is
configured with: the score right now and whether now is a peak, a dip, or a
neutral window.

Returns the current score, the window type, a plain-language recommendation,
and today's peak and dip times. Meant as a cheap check before an agent
recommends, schedules or starts demanding work.

Choose this tool for "right now". Use whenpeak_best_window to find a slot
later today, and whenpeak_quick_predict when working from sleep the user
describes rather than stored history.

Requires WHENPEAK_API_KEY on the server and reads that one account's
history, so it is only meaningful where the server runs with the user's own
key. Without a key it returns a not_configured error rather than failing.
Read-only and stores nothing, but each call counts against that account's
monthly quota.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and meets it. It discloses the API key prerequisite, that it reads one account's history, that it returns a not_configured error without a key, that it is read-only and stores nothing, and that it consumes monthly quota. This is exemplary transparency beyond the schema.

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?

The description is front-loaded with the core purpose, then output, then usage and caveats. Although it is longer than many tool descriptions, every sentence adds essential information: outputs, intended use, sibling routing, key requirement, error behavior, and quota impact.

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 zero-parameter tool with no output schema, the description is complete. It explains what the tool reports, what it returns, when to use it, prerequisites, failure behavior, and cost. An agent has enough context to invoke it correctly and interpret the result.

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?

There are zero parameters, so the baseline is 4 and there is no parameter detail the description needs to supply. The description correctly focuses on behavior and output instead of inventing parameter-level semantics.

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 leads with a specific verb and resource: "Report the current moment's performance state" and names the exact outputs (score, window type, recommendation, today's peak/dip times). It distinguishes itself from siblings by explicitly stating "right now" versus later-today prediction.

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?

It gives explicit when-to-use guidance: "Meant as a cheap check before an agent recommends, schedules or starts demanding work. Choose this tool for 'right now'." It also names alternatives: whenpeak_best_window for a later slot and whenpeak_quick_predict for user-described sleep, so an agent can route correctly.

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

All WhenPeak tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.9/5.0

Disambiguation5/5

Each tool targets a distinct temporal scope: right now, today's best window, a single day, or a multi-day span. The descriptions explicitly cross-reference when to use each, so an agent should not confuse them.

Naming Consistency4/5

All tools share the whenpeak_ prefix and consistent snake_case, making the set recognizable. However, the suffixes mix noun phrases (best_window, performance_now) with verb phrases (multiday_predict, quick_predict), so the pattern is not perfectly uniform.

Tool Count5/5

Four tools is a well-scoped size for this server's purpose: assessing current performance, finding a window today, predicting one day, and projecting multiple days. No tool feels redundant or missing.

Completeness5/5

The tool surface covers the main prediction workflows: current state, today's slot, single-day curve, and multi-day forecast. Since the server is read-only prediction, CRUD operations are not expected, and there are no obvious dead ends.

Resources

Need Help?