Skip to main content
Glama
futureweb

Futureweb Intervals MCP

by futureweb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

analyze_climbs

Read-only

Split any activity recording into climbs, descents, sections and pauses by analyzing grade and speed. Get per-segment time, distance, gain, grade, VAM, power and HR for tours, hikes and trail runs.

Instructions

Use for activities without useful intervals (tours, mountain hikes, trail runs) to split the recording into climbs, descents, sections in between and pauses.

Per segment: time and sample indices, moving time, distance, gain/loss, average and steepest grade, VAM, speed, power, NP, HR, cadence and start/end/min/max/mean/delta of every custom stream. Defaults follow the sport (foot vs bike); implausible grades are flagged and each segment gets a grade confidence. Slow scrambling counts as moving, real pauses as pause. Climb gains are not the activity's total elevation gain. Text lists up to max_segments segments. Read-only, 2 API calls (activity, all streams). Method: intervals://methods/climbs (get_guide).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activity_idYesActivity id, e.g. i123456789
max_segmentsNoSegments listed in text output
min_grade_pctNoMinimum average grade of climbs and descents, %
output_formatNojson = machine-readable, all fieldstext
grade_window_mNoDistance window of the steepest grade, metres; default 50 on foot, 100 otherwise
pause_min_secsNoMinimum length of a reported stationary period, seconds
show_raw_gradeNoAlso report the grade of the unsmoothed altitude (windows of at least min_grade_distance_m)
min_climb_gain_mNoMinimum elevation gain of a climb, metres
extra_stream_typesNoComma-separated standard streams to evaluate per segment besides the custom ones, e.g. temp,respiration,left_right_balance
min_descent_loss_mNoMinimum elevation loss of a descent, metres
min_grade_distance_mNoNo grade below this horizontal distance, metres; default 30 on foot, 50 otherwise
stationary_speed_m_sNoPause candidate below this speed, m/s; default 0.3 on foot, 0.5 otherwise

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real behavioral context: two API calls (activity + all streams), a method reference via get_guide, the moving-vs-pause rule, grade confidence flagging, and the caveat that climb gains are not total elevation gain. These are meaningful disclosures beyond the annotations, though error/permission behavior is not covered.

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-loads the use case, then packs per-segment fields, defaults, caveats, and cost into a dense but scannable block. Every sentence carries information, though the middle paragraph is thick enough to slow reading slightly.

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?

With 12 parameters and no output schema, the description carries the return-value burden and does list the emitted per-segment fields and text-vs-json behavior. Cost, method guide, and key caveats are present; only edge cases like invalid activity ids are unaddressed.

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 100%, so the baseline is 3, but the description adds non-obvious semantics: defaults vary by sport (foot vs bike), max_segments applies to the text listing, and segment thresholds interact with grade confidence. This meaningfully complements the schema.

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?

States a specific verb (analyze/split) and resource (climbs, descents, sections, pauses) and scopes it to recordings without meaningful intervals. This clearly separates it from the interval-oriented siblings like get_activity_intervals or find_similar_intervals.

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 when-to-use trigger: activities without useful intervals such as tours, mountain hikes, and trail runs. It implies but does not explicitly name the alternative (interval analysis) or state exclusions, so it stops just short of a full routing rule.

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