CourseProfiler

Get runner profile requirements

get_runner_profile_requirements

Read-onlyIdempotent

Use this when runner input is missing or unclear. Explains how to obtain or generate runner input, what USRProf/evidence files should contain, whether GPX/FIT activities are enough, and how hosted MCP clients should upload artifacts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`warnings`	Yes
`workflow`	Yes
`recommended`	No
`upload_flow`	Yes
`accepted_inputs`	Yes
`profile_purpose`	No
`required_fields`	No
`evidence_guidance`	Yes
`how_to_get_usrprof`	Yes
`ask_before_generating`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 14, 2026

addedOutput schema / properties / ask_before_generating

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / profile_purpose

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedJul 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description describes an informational/read-only behavior ('Explains...') and does not contradict the annotations of readOnly, idempotent, and non-destructive. It adds useful context about the topics covered, though it does not explicitly restate the read-only nature, which is already provided by the annotations.

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 a single well-structured sentence that front-loads the usage trigger and then lists the key topics covered. It contains no redundant or filler content, making it efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a requirements tool with no parameters and an implied informational output, the description covers all essential aspects: how to obtain or generate input, expected file contents, acceptable activity formats, and upload instructions for hosted MCP clients. Nothing critical is missing.

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?

The tool has zero parameters in its schema, so there are no parameters to document or clarify. Per the baseline for tools without parameters, a score of 4 is appropriate.

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 clearly states the tool's purpose: it provides requirements for runner input, detailing file contents, acceptable activity formats, and upload instructions. It is easily distinguishable from sibling 'requirements' tools by its specific focus on runner profile data (USRProf, GPX/FIT).

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 explicitly says 'Use this when runner input is missing or unclear,' giving a clear trigger for when to call the tool. It does not explicitly mention sibling alternatives or when not to use it, but the runner-specific context makes the appropriate usage evident.

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?