CourseProfiler

Generate course segments

generate_course_segments

Generate analytical course segments from an enriched CRSProf artifact after waypoint enrichment, or from a catalog CRSProf that already contains official waypoints/resources/cutoffs; then use the resulting artifact in create_race_plan for race planning, or call submit_course if and only if the user asked to submit a course for catalog review. A generated CRSProf artifact is not a catalog submission.

Input Schema

Name	Required	Description	Default
`options`	No
`crsprof_artifact_id`	Yes	Enriched CRSProf artifact ID returned by enrich_course_waypoints.

Output 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.
`submission_request_id`	No	Request ID that originally allocated this job; absent in legacy metadata.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

addedOutput schema / properties / submission_request_id

Added value: +{
+  "description": "Request ID that originally allocated this job; absent in legacy metadata.",
+  "type": "string"
+}

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."

First observedJul 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and direct the safety profile, so the bar is lower. The description still adds meaningful state context: it requires enriched input, produces an artifact for downstream steps, and clarifies 'A generated CRSProf artifact is not a catalog submission'. It does not discuss repeat-call/idempotency behavior despite idempotentHint=false, leaving that gap.

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?

Front-loaded with the core action, then workflow routing. Two dense semicolon-joined sentences; no filler sentences, though the second sentence is long and clause-heavy.

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-value explanation is unnecessary, and annotations carry the mutation/safety profile. Prerequisites, downstream routing, and the submission distinction are covered, giving an agent enough to place and call it correctly, with only option-parameter semantics and idempotency left unaddressed.

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 50% of top-level parameters are documented (crsprof_artifact_id; options has no description), so the description should compensate but does not name or explain any option. The nested options sub-properties are individually well-described in the schema, which partially offsets the gap. Description adds no parameter meaning beyond the schema, so baseline 3 is warranted.

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 verb and resource ('Generate analytical course segments') and grounds it in a concrete input artifact (CRSProf). It distinguishes itself from siblings by naming the upstream producer (enrich_course_waypoints) and downstream consumers (create_race_plan, submit_course).

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?

States the two valid input conditions ('after waypoint enrichment, or from a catalog CRSProf that already contains official waypoints/resources/cutoffs') and where the output should route ('use the resulting artifact in create_race_plan... or call submit_course if and only if the user asked to submit'). The 'if and only if' clause is an explicit exclusion that prevents misuse.

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?