Skip to main content
Glama

get_weekly_stress

Read-only

Fetches weekly stress aggregates ending on a specified date for a chosen number of weeks, enabling review of stress trends over time.

Instructions

Get weekly stress data aggregates

    Returns weekly stress values for the specified number of weeks ending at end_date.

    Args:
        end_date: End date in YYYY-MM-DD format
        weeks: Number of weeks to fetch (default 4, max 52)
    

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": {
      "end_date": "<end_date>"
    },
    "name": "get_weekly_stress"
  }
}

Input Schema

NameRequiredDescriptionDefault
weeksNo
end_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavior context: results are weekly buckets ending at a given date and are capped at 52 weeks. It does not disclose what a 'stress value' represents (units, scale, or averaging method) or how partial weeks are handled.

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?

Short and front-loaded: one sentence of purpose followed by a single sentence on the return window. The docstring-style 'Args:' block is somewhat redundant with the schema but earns its place by supplying the format and bounds that the schema lacks.

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?

For a small two-parameter read tool with annotations covering safety, this is close to adequate, but with no output schema the description should say more about the shape of the returned weekly series (per-week fields, ordering). As written, the agent knows how to call it but not what it will get back.

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 description coverage is 0%, so the description carries the full burden, and it does so well: end_date is documented as YYYY-MM-DD, weeks is documented with a default of 4 and a maximum of 52. It leaves the week-boundary convention (rolling seven-day buckets vs calendar weeks) ambiguous, which prevents a 5.

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

Purpose4/5

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

The description states a specific verb and resource, 'Get weekly stress data aggregates', and clarifies the scope as weekly stress values over a window ending at end_date. It does not, however, distinguish this from siblings such as get_stress_data, get_stress_summary, or get_all_day_stress, so an agent must infer which granularity to pick.

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 explicit when-to-use guidance, no stated prerequisites, and no mention of alternatives despite several stress-related siblings. The word 'aggregates' implies a summary-granularity use case, but the agent is left to infer it.

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