Skip to main content
Glama

get_stress_summary

Read-only

Returns a compact stress summary for a specified date, providing essential metrics instead of full time-series data for daily health checkups and LLM integrations.

Instructions

Get stress summary with essential metrics (lightweight version)

    Returns a compact summary (~400 bytes) instead of full time-series data (~35KB).
    Ideal for daily health checkups and LLM integrations.

    Args:
        date: Date in YYYY-MM-DD format
    

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": {
      "date": "<date>"
    },
    "name": "get_stress_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: approximate response size (~400 bytes vs ~35KB) for planning. It says nothing about which stress metrics are included, rate limits, or auth.

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?

Front-loaded with the key distinction (summary vs full data) and sized proportionally to a simple one-parameter tool. The docstring-style 'Args:' block is slightly noisy but carries the format detail that the schema omits.

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 read-only single-parameter tool with no output schema, an agent gets enough to call it correctly: what it returns in general terms, its size, and the date format. The main remaining gap is which metrics the summary actually contains.

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 coverage is 0% - the schema only declares 'date' as a bare string with title 'Date'. The description supplies the required format (YYYY-MM-DD), which is real added meaning and fully covers the single parameter, but stops short of timezone or range semantics.

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?

States a specific verb and resource ('Get stress summary') and immediately scopes it as the 'lightweight version' returning a compact summary rather than full time-series data. This implicitly separates it from the heavier stress-data siblings, though it never names them.

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

Usage Guidelines4/5

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

Gives a clear selection condition: use this when a ~400-byte summary suffices (daily checkups, LLM integrations) rather than the ~35KB time-series. The alternative is described by payload rather than by tool name, so there is no explicit 'use X instead' routing.

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