Skip to main content
Glama

List WWDC sample code projects

wwdc_sample_code_list
Read-onlyIdempotent

Browse indexed WWDC sample code projects by year, topic, or kind to find downloadable code and linked sessions.

Instructions

Browse all indexed sample code projects with optional year and topic filters. Returns title, URL, kind (zip/github/snippet), and the linked session. Grouped by year.

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_sample_code_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoSample code kind filter, e.g. 'zip', 'github'.
yearNoFilter to a specific WWDC year.
limitNo
topicNoSession topic substring filter, e.g. 'SwiftUI', 'Swift', 'visionOS'.
formatNoResponse formatmarkdown
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / year / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / year / minimum
      Added value: +-9007199254740991
  2. First observedv0.2.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered and the description only needs to add context. It does add the return shape (title, URL, kind, linked session) and the "Grouped by year" output structure, but says nothing about pagination, default page size, or how many projects exist in the index.

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?

Three short sentences with the browse scope front-loaded, filters second, and return shape third. Every sentence carries information; only the trailing "Grouped by year" is a slightly dangling detail that could have been folded into the return-shape sentence.

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?

With no output schema, the description correctly compensates by naming the returned fields and the grouping, which is the most important missing structured information. However, for a 6-parameter paginated list tool it omits limit/offset behavior and default page size, leaving the agent to discover pagination from the schema alone.

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 67%, and the description only restates the year and topic filters already documented in the schema. It adds a little by enumerating kind values (zip/github/snippet), which slightly exceeds the schema's tag description, but limit, offset and format are never addressed in the description. Baseline 3 is appropriate.

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 gives a specific verb and resource ("Browse all indexed sample code projects") and scopes it with optional year/topic filters, so the agent knows this is a listing endpoint rather than a lookup. It does not name the near-siblings (wwdc_sample_code_grep for searching, wwdc_list_session_code for code tied to one session), so the differentiation is inferable rather than explicit.

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?

"with optional year and topic filters" implies the browse-with-filters use case, but there is no statement of when to prefer this over wwdc_sample_code_grep or wwdc_list_session_code, and no exclusions. The usage is implied rather than prescribed.

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