Crawlora MCP

strava_club

Read-only

Fetch a Strava club's public profile, including its name, location, membership count, and images; private member, discussion, leaderboard, and activity data are unavailable without login. Use strava_routes for route recommendations or strava_challenges for the public challenge gallery.

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": {
      "id": "<id>"
    },
    "name": "strava_club"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Strava club ID

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / id / description
```
Added value: +"Strava club ID"
```
First observedOct 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, so safety is covered; the description adds real value by disclosing the authentication boundary — which parts of the club profile are unavailable without login. It does not describe rate limits or freshness, but the added scope disclosure is meaningful.

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, front-loaded with the payload contents, then the access limitation, then sibling routing. No filler.

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 need not be re-explained, and the description already covers scope and authentication constraints. Complete enough for a single-parameter read tool, with only minor room on identification format.

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?

Only one parameter ('id') with 100% schema description coverage, so the schema already documents it. The description adds no format hints (e.g., numeric vs slug) beyond what the schema provides, which is the expected baseline.

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?

Specific verb ('Fetch') plus a clearly scoped resource ('a Strava club's public profile') and an enumeration of returned fields (name, location, membership count, images). An agent can distinguish this from siblings like strava_routes and strava_challenges without opening the schema.

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?

States the boundary condition (private member/discussion/leaderboard/activity data require login) and names two siblings, but the named siblings solve unrelated tasks (route recommendations, challenge gallery) rather than being genuine alternatives for club lookup, so the routing guidance is only loosely useful.

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

All Crawlora MCP tools Inspect

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

Need Help?