Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

strava_routes

Read-only

List public Strava route recommendation records for a sport and region, one page at a time. Use strava_route_detail with a returned route path when you need one route's distance, elevation, or summary.

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": {
      "sport": "<sport>",
      "country": "<country>",
      "region": "<region>"
    },
    "name": "strava_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1
sportYesRoute sport. Allowed values: hiking, road-biking, mountain-biking, trail-running, gravel-biking. Documented values: hiking, road-biking, mountain-biking, trail-running, gravel-biking.
regionYesRegion slug: a state (colorado) or state/city (colorado/boulder)
countryYesCountry slug, e.g. usa

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / country / description
      Added value: +"Country slug, e.g. usa"
    • addedInput schema / properties / page / description
      Added value: +"Page number, starting at 1"
    • addedInput schema / properties / region / description
      Added value: +"Region slug: a state (colorado) or state/city (colorado/boulder)"
    • addedInput schema / properties / sport / description
      Added value: +"Route sport. Allowed values: hiking, road-biking, mountain-biking, trail-running, gravel-biking. Documented values: hiking, road-biking, mountain-biking, trail-running, gravel-biking."
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety and openness profile. The description adds useful scope detail ('public', 'recommendation records') and pagination behavior ('one page at a time'), but says nothing about licensing/auth requirements, rate limits, or result set size. With annotations carrying the safety burden, a 3 is appropriate — it adds modest context but not rich behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with zero waste. The core capability and scoping are front-loaded, and the sibling routing follows immediately. Every clause earns its place.

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?

An output schema exists, so return values and the 'route path' shape need not be described here, and the full-schema coverage handles the parameters. The description covers purpose, pagination, and the alternative, leaving only minor gaps such as page size or how to advance pages, which the page parameter already implies.

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 description coverage is 100%, with sport, country, region, and page all documented in the schema itself. The description only restates the sport-and-region scoping, adding no enum, slug-format, or paging syntax detail beyond the schema. Baseline 3 is correct when the schema does the heavy lifting.

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 (List), the exact resource (public Strava route recommendation records), and the scoping dimensions (sport and region), plus the pagination unit. It names the sibling strava_route_detail and what that sibling is for, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Explicitly names the alternative (strava_route_detail) and the condition that selects it ('when you need one route's distance, elevation, or summary'), including the prerequisite 'with a returned route path'. This mirrors the high-quality routing pattern of stating what this tool is not for.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources