Skip to main content
Glama

get_running_tolerance_trend

Read-only

Track running tolerance trends over a date range to see whether load capacity is rising or falling and how intensity changes the cost of each kilometer.

Instructions

Get Running Tolerance trend over a date range.

    Running Tolerance moves slowly — its value is in the trajectory, not any
    single day. Returns, per period: tolerance_km (current load capacity),
    acute_load_km (intensity-adjusted load), distance_km (actual distance
    run), and load_ratio (acute_load_km / distance_km — how much intensity
    inflates the cost of each kilometer). Weekly aggregation (default) gives
    a compact multi-month view; daily gives day-to-day resolution for a
    shorter window.

    Recommended range: 4-12 weeks. Maximum: 90 days for daily aggregation,
    366 days for weekly (this endpoint returns the whole range in one call,
    so the limit protects output size, not request volume).

    Args:
        start_date: Start date in YYYY-MM-DD format
        end_date: End date in YYYY-MM-DD format
        aggregation: "daily" or "weekly" (default "weekly")
    

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

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes
aggregationNoweekly

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral facts: the whole range is returned in a single call with no pagination, and the hard caps (90 days daily, 366 days weekly) exist to protect output size rather than request volume. That is useful but largely re-framed as argument guidance, so it sits just above the annotated baseline.

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 a one-line purpose, then progressively more detail in an ordered, scannable layout; the numeric caps and field definitions all earn their place. The prose is slightly verbose and could be trimmed without losing meaning.

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?

With no output schema, the description compensates by defining every returned field (tolerance_km, acute_load_km, distance_km, load_ratio) including the derivation of load_ratio. Range limits, aggregation tradeoffs and date formats are all present, leaving nothing an agent needs in order to call it correctly.

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

Parameters5/5

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

Schema coverage is 0% (bare titles only), so the description must carry the full burden and does: it specifies the YYYY-MM-DD format for both dates, and explains that aggregation accepts daily or weekly with weekly as default and what each choice yields. No parameter is left ambiguous.

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 (Get) and resource (Running Tolerance trend) with an explicit date-range scope, and clarifies that the metric is meaningful as a trajectory rather than a single-day snapshot. It implies but never names the sibling get_running_tolerance as the tool for the current value, so differentiation is suggested rather than stated.

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 concrete selection guidance between the two aggregation modes (weekly = compact multi-month view, daily = day-to-day resolution over a shorter window) plus a recommended 4-12 week range. What is missing is any explicit statement of when not to use this tool, e.g. deferring to the point-in-time sibling.

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