csa-skilljar

Official

Overview Schema Source Related Servers Discussions Admin

check_access

Read-onlyIdempotent

Check which Skilljar API credentials are configured and working, and what each unlocks. When a credential problem appears, run this first to identify the failing API instead of retrying.

Instructions

Which Skilljar credential is configured and working, and what each one unlocks.

Call this first whenever a tool reports a credential problem, and relay what it says rather than retrying - a retry fails identically. This server holds two INDEPENDENT credentials, one per Skilljar API, so "v2 works, v1 does not" is a normal state and a capability that looks unsupported may be one environment variable away.

Needs no credential itself and makes no call to Skilljar when nothing is configured, so it answers even when everything else fails. Returns no secret material - only whether each credential is set, and which scopes were granted.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`v1`	Yes
`v2`	Yes
`profile`	Yes
`version`	Yes
`granted_scopes`	Yes
`scopes_unknown`	No
`expires_in_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.13.0Aug 29, 2026
- addedOutput schema / properties / scopes_unknown
```
Added value: +{
+  "title": "Scopes Unknown",
+  "type": "boolean"
+}
```
First observedv0.1.0Aug 27, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behaviors: the server holds two independent credentials, partial availability is normal, it makes no external call when nothing is configured, and it never returns secret material. This gives the agent accurate expectations and prevents incorrect assumptions about failure states.

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 appropriately sized and front-loads the core purpose in the first line. Each subsequent sentence adds distinct value: usage timing, credential independence, offline behavior, and output safety. There is no redundant or filler content.

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?

Given the zero-parameter schema, the safe annotations, and the presence of an output schema, the description covers all necessary context: when to call, what to expect, how to interpret partial states, and what is not returned. Nothing an agent needs to invoke this tool correctly 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, so there is nothing for the description to add about parameter meanings. The schema fully covers the input side, and the description appropriately notes that the tool needs no credential itself, which is the only input-related nuance worth stating.

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 exactly what the tool does: it reports which Skilljar credential is configured, working, and what each unlocks. It is clearly a diagnostic tool and is distinguishable from the capability-oriented siblings like describe_capabilities by its focus on credential readiness.

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?

The description gives explicit usage direction: call it first whenever a tool reports a credential problem, and relay its output instead of retrying because retries fail identically. It also clarifies that it works even when other tools fail, which tells the agent when to prefer this tool over alternatives.

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

Deploy Server