Skip to main content
Glama
Sign In
skepsis

skepsis

by ionpetro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List the course

list_course
Read-only

Lists all course units and lessons with done/open/locked status and identifies the next lesson, helping you choose a lesson ID to start.

Instructions

Show every unit and lesson with done/open/locked status and which lesson is next. Use it to pick a lesson id for start_lesson.

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": "list_course"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

readOnlyHint already covers the safety profile, so the description's value is in disclosing return content: per-lesson status values and the next-up lesson. There is no output schema, so this disclosure matters, though ordering, size, and whether the course is implicit are not addressed.

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?

Two sentences with zero filler; the content of the response is front-loaded and the call-to-action follows. Nothing repeats the name or title.

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 parameterless read tool with annotations and no output schema, the description covers what comes back and what to do with it. A note on scope (single user's course) or ordering would close the remaining gap.

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 the baseline applies. The description correctly implies no input is needed to enumerate the single course.

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?

States a specific verb and resource plus exactly what the listing contains: units, lessons, done/open/locked status, and the next lesson. That distinguishes it from siblings like progress, which implies aggregate stats rather than a navigable course outline.

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?

Explicitly routes the agent to start_lesson by saying the tool is for picking a lesson id. It gives no when-not guidance (e.g. how it differs from progress), but the positive usage condition is unambiguous.

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

Deploy Server

Other Tools