Skip to main content
Glama
Sign In
Running Companion MCP Server

Running Companion MCP Server

by Dtsiakas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid
This server has been deprecated

Personal project, not offered for public use.

When to run

get_run_forecast
Read-only

Fetch hourly running-weather forecasts for today's remaining and tomorrow's running hours, including temperature, humidity, wind, rain chance, heat-adjusted slowdown, dry window, and hour to avoid.

Instructions

Hourly forecast for today's remaining hours and tomorrow (06:00 to 22:00) where the user usually runs, from Open-Meteo: air temperature, dew point, humidity, wind, chance of rain, and the heat cost of each hour (Hadley's temperature plus dew point rule: estimated % slower at the same effort). Each day has the coolest dry window and the hour to avoid. Clock hours are local. A run's own weather and heat-adjusted pace are in get_activity.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint; the description adds meaningful context beyond them: the upstream provider (Open-Meteo), the location scoping rule ('where the user usually runs'), the local-clock convention, and the derivation of the heat-cost field via Hadley's temperature-plus-dew-point rule. It does not mention latency, caching, or failure modes for the external call, which keeps it short of a 5.

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 and time window are front-loaded, and each sentence carries distinct information (metrics, derivation, per-day summary, timezone, sibling handoff). It is dense but slightly long, with parenthetical explanation of the heat rule that could be trimmed.

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 input parameters and no output schema, the description must describe the returned data itself — and it does, enumerating the hourly fields and the per-day 'coolest dry window' and 'hour to avoid' summaries. An agent knows what it will get without any further documentation.

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?

The tool takes zero parameters, so the schema baseline is a 4. The description usefully clarifies that location is not user-specified but fixed to where the user usually runs, and that effects are read from the existing activity data rather than passed in.

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?

Names a specific resource and scope — 'hourly forecast for today's remaining hours and tomorrow (06:00 to 22:00) where the user usually runs' — plus the data source and exact metric list. It also explicitly distinguishes itself from the sibling get_activity, which covers a single run's own weather.

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?

Usage is clearly implied by the title and content (deciding when to run in the next ~1.5 days), and the closing sentence routes the agent to get_activity when it wants a specific run's weather instead. There is no explicit 'do not use this for X' exclusion, but the one realistic alternative is named.

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