CourseProfiler

Build runner profile from Strava

build_runner_profile_from_strava

Build a USRProf from Strava activities selected for a target course or distance. Ask the user for the target course or distance and, when an existing profile is supplied, explicitly ask whether to merge or replace. Strava credentials are never accepted through MCP: this tool returns a private one-hour browser authorization URL and resumes the same job after authorization. If evidence is insufficient, relay the structured user decision and resume the same job with build_anyway, broaden_filters, or cancel.

Input Schema

TableJSON Schema

Name	Required	Description
`course`	No
`filters`	No
`decision`	No
`course_file`	No	Inline/proxied GPX, FIT, CRSProf, or ZIP-with-one-GPX target course, using the same convention as create_race_plan.
`resume_job_id`	No	Existing waiting Strava profile-build job to resume.
`target_distance_m`	No	Target distance in metres when no course is supplied. Ask the user before choosing it.
`existing_profile_strategy`	No	Required whenever existing_usrprof_artifact_id is supplied; ask the user explicitly.
`existing_usrprof_artifact_id`	No	Existing USRProf artifact to merge with or replace.

Output Schema

TableJSON Schema

Name	Required	Description
`errors`	No
`job_id`	Yes	CourseProfiler job ID to poll with get_job.
`status`	Yes	Job status, e.g. queued, running, succeeded, or failed.
`progress`	No
`warnings`	No
`created_at`	No	ISO-8601 creation timestamp.
`expires_at`	No	ISO-8601 expiration timestamp.
`started_at`	No	ISO-8601 start timestamp, when available.
`status_url`	No	Relative API URL for polling this job.
`completed_at`	No	ISO-8601 completion timestamp, when available.
`result_artifacts`	No	Artifacts produced by the job, including role metadata.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026

changedOutput schema / properties / result_artifacts / items / properties / download_url / description

Previous value: -"Private short-lived download URL. Share only with the user."New value: +"Artifact download URLs are private and short-lived; share them only with the user, verbatim in a code block, not a clickable link. Ask the user to copy the entire URL into their browser address bar. Do not rewrite the URL or add tracking parameters such as utm_source: changes invalidate the signature. If expired, call get_artifact for a fresh URL. This applies only to artifact download_url values, not authorization or upload links."

Changed2 schema fields changedAug 28, 2026

addedInput schema / properties / filters / properties / estimation_model / description

Added value: +"Optional runner-profile model. Omit for recommended load_response_evidence_v2; load_response_evidence_v3 is explicit and experimental."

changedInput schema / properties / filters / properties / estimation_model / enum

Previous value: -[
-  "segment_evidence_v1",
-  "load_response_evidence_v1",
-  "load_response_evidence_v2",
-  "load_response_evidence_v3"
-]New value: +[
+  "load_response_evidence_v2",
+  "load_response_evidence_v3"
+]

AddedAug 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already flag non-read-only, non-idempotent, and open-world behavior. The description adds critical specifics: the tool returns a private one-hour browser authorization URL, resumes the same job after authorization, and relays structured user decisions on insufficient evidence. This goes beyond the annotations without contradicting them.

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?

The description is three sentences and front-loads the primary purpose. It efficiently covers the authorization flow and decision handling without excessive length, though it could be slightly more structured with separate clauses for clarity.

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?

Given the complexity (8 parameters, nested objects, output schema, annotations), the description covers the essential flow: user input, merge/replace, authorization, and resume. It does not elaborate on every edge case, but the schema and output schema cover the details, making it sufficiently complete for an agent to invoke it correctly.

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 63%, which is moderate. The description does not add meaning to any specific parameters beyond what the schema already provides; it only references 'target course or distance' and 'existing profile' at a high level. Since the schema carries most of the burden, the description adds minimal parameter-level value.

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?

The description states a specific verb ('Build') and resource ('a USRProf from Strava activities') and clarifies the target selection (course or distance). It distinguishes itself from siblings like generate_runner_profile by explicitly anchoring to Strava activities and the authorization flow.

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?

The description gives clear context on when to use this tool: it requires asking the user for target course/distance, handling merge/replace decisions, and never accepting Strava credentials directly. However, it does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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

All CourseProfiler 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?