Skip to main content
Glama

list_paths

Read-onlyIdempotent

Retrieve the learning paths an organization has defined, including each sequence's title, description, and course count.

Instructions

List the course sequences an organization has defined.

    A path is the SEQUENCE: a title, descriptions, and a count of the courses in it.
    It is NOT what a learner sees. To find that, use `list_published_paths`, which is
    the path on a particular domain, with a URL and visibility.

    `course_name_singular` / `course_name_plural` are what this path calls its steps
    on the customer-facing site - some organizations call them "modules" or "levels"
    rather than "courses". Use those words when describing the path back to someone.

    `path_item_count` is how many courses are in the sequence; `list_path_items`
    gives the ordered list.

    Requires `CSA_SKILLJAR_V1_API_KEY`, a separate credential from the v2 client.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
page_sizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
pageNo
rowsYes
totalNo
has_moreNo
next_pageNo
Install Server

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark this as read-only and idempotent, so the description adds value by disclosing the separate CSA_SKILLJAR_V1_API_KEY requirement and clarifying the internal vs published-path semantics. It does not address pagination behavior, but the output schema covers return shape and the safety profile is already carried by annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and is organized into short, purposeful paragraphs. It is longer than strictly necessary, but each section adds meaning: the distinction from published paths, field semantics, and credential requirements.

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?

With an output schema and standard pagination parameters, the description covers the essential invocation context: credential, path/published distinction, and related item-listing tool. It falls short only in not explaining the page/page_size semantics or distinguishing from list_course_series.

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

Parameters2/5

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

Schema description coverage is 0% and the description says nothing about page or page_size, so an agent gets no parameter semantics beyond their conventional names. The useful field-level explanations (course_name_singular/plural, path_item_count) describe output fields, not the two request parameters, so the low schema coverage is not compensated.

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 opening sentence names a specific verb and resource ('List the course sequences an organization has defined') and immediately disambiguates from list_published_paths by stating what a path is NOT. This lets an agent separate internal path definitions from learner-facing published paths without opening schemas.

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 explicitly directs agents to list_published_paths for learner-visible paths and to list_path_items for ordered course items, giving clear when-to-use vs alternatives. The credential note also states a prerequisite for calling this tool.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CloudSecurityAlliance/csa-skilljar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server