coros-training-mcp

Overview Schema Source Related Servers Discussions Admin

Check Coros Auth

check_coros_auth

Check whether valid Coros access tokens are stored locally so you can verify authentication before accessing COROS training data or scheduling workouts.

Instructions

Check whether valid Coros access tokens are stored locally.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_coros_auth"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Oct 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does contribute one meaningful detail: the check is against tokens 'stored locally,' implying a local read rather than a network round-trip. Beyond that it is silent on whether the call can refresh or mutate tokens, whether it makes any remote request, and whether it is safe to call repeatedly, all of which matter for an auth tool with zero annotation coverage.

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?

A single front-loaded sentence with no filler; the operative scope ('stored locally') arrives before the sentence ends. Nothing could be trimmed without losing information.

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

Completeness3/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 documentation is not needed, and with no parameters the surface area is small. The remaining gap is decision support: an agent that gets a negative result has no stated next step, and for a boolean auth gate that omission is the one thing the description should close.

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 takes zero parameters, so there is nothing for the description to disambiguate; the schema and description cannot conflict. Baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Check') and a precise resource ('valid Coros access tokens stored locally'), so there is no ambiguity about what the call does. It is distinguishable from the authenticate_* siblings by being a status probe rather than a login flow, though it never names those siblings explicitly to reinforce the split.

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?

Usage is only implied: the tool's shape makes it obvious it is a precondition probe, but the description never says when to call it (e.g., before any data call) or what to do when the check fails. It also does not point to authenticate_coros / authenticate_coros_mobile as the follow-up path, which is the most valuable guidance an agent could get here.

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