Skip to main content
Glama

get_lactate_threshold

Read-only

Retrieve lactate threshold data by date range or latest reading to identify the exercise intensity where lactate accumulates, helping guide endurance training.

Instructions

Get lactate threshold data

    Returns lactate threshold information, which is the exercise intensity at
    which lactate starts to accumulate in the blood. This is a key metric for
    endurance training.

    Args:
        start_date: Start date in YYYY-MM-DD format (optional; give with
            end_date for history, omit both for latest)
        end_date: End date in YYYY-MM-DD format (optional; give with
            start_date for history, omit both for latest)
    

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_lactate_threshold"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNo
start_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 helpful behavioral context about the two calling modes (history vs latest) but says nothing about what shape results take — a single value, a daily series, or per-activity records — which matters for a metrics endpoint.

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?

Purpose is front-loaded in the first line, and the parameter notes follow in a predictable order. The explanatory sentence about what lactate threshold means is slightly padded but plausibly useful for disambiguation, leaving little genuine waste.

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 two-optional-parameter read tool with no output schema, the description covers calling conventions adequately but leaves the return shape undefined — an agent cannot tell whether to expect one record or a time series. The metric definition is a nice touch, but the missing response characterization is the notable gap.

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 coverage is 0%, so the description must carry the parameters, and it does: date format (YYYY-MM-DD), the requirement that start and end be supplied together, and the both-omitted behavior returning the latest reading. It stops short of covering edge cases such as passing only one of the pair or how inclusive the range is.

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 lactate threshold data") and even defines the metric so an agent knows what domain it belongs to. It does not name or contrast a sibling tool, but the resource is distinctive enough among the get_* fitness-metric siblings to be unambiguous.

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

Usage Guidelines3/5

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

Guidance is about invocation rather than when-to-choose: it explains that both dates give history and omitting both returns the latest value. There is no explicit statement of when to prefer this over related tools or any prerequisites/limits, so usage is implied rather than guided.

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