Skip to main content
Glama

CourseProfiler

by com.courseprofiler
OverviewDiscussionsAdmin

Enrich course waypoints

enrich_course_waypoints

Add structured aid stations, checkpoints, cutoffs, and canonical resources to a CRSProf artifact that lacks them. Before enriching, inspect whether the imported source already contains GPX/CRSProf waypoints; if it already contains GPX/CRSProf waypoints, avoid duplicate Start/Finish/aid stations and prefer merging/updating resources, cutoffs, notes, or links on existing waypoint metadata. Prefer waypoints.mode=structured; put non-canonical/free-text aid details in notes/source text because unsupported resource strings are ignored with warnings. Route-only plans should be labeled incomplete unless the CRSProf already includes official waypoints/resources/cutoffs or the user explicitly accepts missing aid/resource details.

Input Schema

NameRequiredDescriptionDefault
waypointsYes
crsprof_artifact_idYesCRSProf artifact ID returned by import_course or get_artifact.

Output Schema

NameRequiredDescriptionDefault
errorsNo
job_idYesCourseProfiler job ID to poll with get_job.
statusYesJob status, e.g. queued, running, succeeded, or failed.
progressNo
warningsNo
created_atNoISO-8601 creation timestamp.
expires_atNoISO-8601 expiration timestamp.
started_atNoISO-8601 start timestamp, when available.
status_urlNoRelative API URL for polling this job.
completed_atNoISO-8601 completion timestamp, when available.
result_artifactsNoArtifacts produced by the job, including role metadata.
submission_request_idNoRequest ID that originally allocated this job; absent in legacy metadata.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / submission_request_id
      Added value: +{
+  "description": "Request ID that originally allocated this job; absent in legacy metadata.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • 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."
  3. Changed1 schema field changed
    • changedInput schema / properties / waypoints / properties / items / items / properties / resources / items / enum
      Previous value: -[
-  "water",
-  "water_source",
-  "drinks",
-  "fruit",
-  "food",
-  "toilet",
-  "medic",
-  "chrono",
-  "crew",
-  "pacer",
-  "car",
-  "bus",
-  "ambulance",
-  "shuttle",
-  "drop_bag",
-  "withdrawal",
-  "binoculars",
-  "hot_meal",
-  "tent",
-  "showers",
-  "changing_room",
-  "physiotherapy",
-  "rest_area",
-  "start_flag",
-  "finish_flag"
-]New value: +[
+  "water",
+  "water_source",
+  "drinks",
+  "fruit",
+  "food",
+  "toilet",
+  "medic",
+  "chrono",
+  "crew",
+  "pacer",
+  "car",
+  "bus",
+  "ambulance",
+  "shuttle",
+  "telecabine",
+  "drop_bag",
+  "withdrawal",
+  "binoculars",
+  "hot_meal",
+  "tent",
+  "showers",
+  "changing_room",
+  "physiotherapy",
+  "rest_area",
+  "start_flag",
+  "finish_flag"
+]
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already disclose the mutation profile (readOnly=false, idempotent=false, destructive=false, openWorld=true), so the bar is lower. The description adds real behavioral context beyond that: duplicate avoidance, merge-vs-add preference, warnings emitted for unsupported resource strings, and incomplete labeling for route-only plans.

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 core action is front-loaded in the first sentence and every subsequent sentence adds a distinct constraint. It is dense but not padded; sentences are long, which slightly hurts scannability.

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 explained. Combined with annotations covering the mutation profile and the description covering edge cases (duplicates, warnings, incomplete route-only plans), the definition is close to complete; only the exact success/partial-warning response shape is left to the schema.

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 coverage is 50% and nested fields (items, resources, cutoff, distance) are well documented in the schema itself. The description reinforces mode=structured preference and where to place free-text details, but much of this is already stated in the mode and resources schema descriptions, so added value is marginal.

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+resource ('Add structured aid stations, checkpoints, cutoffs, and canonical resources to a CRSProf artifact') and scopes it to artifacts 'that lacks them.' This distinguishes it from sibling import_course (which brings in the course) and validate_course_profile (which checks one).

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?

Gives explicit conditional guidance: inspect whether the source already has GPX/CRSProf waypoints, and if so prefer merging/updating over adding duplicates. It also states the fallback behavior (route-only plans labeled incomplete unless official waypoints exist or the user accepts the gap).

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

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