Skip to main content
Glama

List learning pathways

wwdc_list_pathways
Read-onlyIdempotent

Lists curated and auto-derived Apple learning pathways for SwiftUI, visionOS, Swift 6, AI, and related topics so you can choose a structured study track.

Instructions

Curated + auto-derived Apple learning pathways (SwiftUI, visionOS, Swift 6, AI, etc.).

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

Input Schema

NameRequiredDescriptionDefault
formatNoResponse formatmarkdown
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.3
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.2.1

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety behavior is fully covered. The description's only added signal is that some pathways are 'auto-derived' rather than curated, a mild quality caveat, but it says nothing about how many pathways return, how the default markdown vs json format differ in shape, or how category filtering behaves.

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?

A single compact sentence with no wasted words, and the topical scope is front-loaded. It is efficient but slightly under-specified rather than padded.

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

Completeness2/5

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

For a two-parameter list tool with no output schema, the description should at least explain what the returned list contains (titles, IDs, counts), the default format, and how the undocumented 'category' filter matches. None of that is present, leaving the agent to experiment.

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

Parameters3/5

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

Schema coverage is 50%: the 'format' enum is documented in the schema, while 'category' has no description at all. The parenthetical topic list (SwiftUI, visionOS, Swift 6, AI) loosely hints at what category values look like, which is useful but not an explicit statement of accepted values or match semantics.

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

Purpose3/5

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

The description is a noun phrase describing the content ('Curated + auto-derived Apple learning pathways') rather than stating an action; the verb 'list' comes only from the title and tool name. The topic examples (SwiftUI, visionOS, Swift 6, AI) do convey scope, but the description never distinguishes this from the sibling wwdc_get_pathway, which fetches a single pathway.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of when to call wwdc_get_pathway instead of this list tool, and no note that this is the entry point that yields IDs for the detail tool. The agent must infer the discover-then-fetch workflow entirely on its own.

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