CourseProfiler

Export race plan PDF

export_race_plan_pdf

Export a Hi-Fi PDF or standalone checkpoint card from an existing CRSProf artifact. The CRSProf supplies the course/profile/plan data; options are presentation-only overrides such as title, subtitle, metric/imperial unit system, format, and file name. Omit unit_system unless the user explicitly asks for metric or imperial.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`options`	No
`crsprof_artifact_id`	Yes	Existing CRSProf artifact ID containing the course/profile/plan data to render.

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

Changed1 schema field changedAug 26, 2026

addedInput schema / properties / options / properties / format

Added value: +{
+  "description": "Set to checkpoint_card for the standalone race-day checkpoint card; omit for the Hi-Fi course profile.",
+  "enum": [
+    "checkpoint_card"
+  ],
+  "type": "string"
+}

AddedJul 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds behavioral context beyond the annotations by clarifying that the CRSProf supplies the data and that options are presentation-only overrides, implying the underlying artifact is not modified. It does not fully detail output file side effects or permissions, but given the annotations are all non-contradictory, this is solid disclosure.

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?

The description is compact and front-loaded: it states the action and resource first, then summarizes the option roles, then gives the critical unit_system guardrail. Every sentence earns its place with no repetition of the title or schema.

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?

For a tool with an output schema, nested options, and one required ID parameter, the description gives enough to call it correctly: what the input artifact provides, what the options affect, and when to omit a parameter. It could go further by noting whether the result is returned directly or saved asynchronously, but the output schema likely covers return behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 50% schema coverage, the description compensates by enumerating the key option fields and adding a specific, non-obvious instruction: 'Omit unit_system unless the user explicitly asks for metric or imperial.' It also clarifies that format distinguishes checkpoint_card from the default Hi-Fi PDF, adding meaning the raw schema does not fully convey.

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 action ('Export') on a specific resource ('existing CRSProf artifact') and names the exact delivery forms ('Hi-Fi PDF or standalone checkpoint card'). This clearly differentiates the tool from siblings like create_race_plan or get_artifact, since it is about rendering an existing plan rather than creating or fetching one.

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?

The description gives clear context that this tool works on an existing CRSProf artifact and that options are presentation-only, which implies the right situation. However, it never explicitly contrasts this tool with alternatives or states when not to use it, leaving tool-selection guidance mostly implicit.

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?