Skip to main content
Glama

List WWDC years

wwdc_list_years
Read-onlyIdempotent

Lists the WWDC years available in the local index with session counts, helping you confirm which conference years are indexed before querying sessions.

Instructions

Returns the set of WWDC years present in the local index with session counts.

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

Input Schema

NameRequiredDescriptionDefault
formatNoResponse formatmarkdown

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so safety is covered. The description still adds real context by scoping the result to years 'present in the local index' (implying coverage is limited to ingested content, not all WWDC history) and by describing the returned shape, which matters since there is no output schema.

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?

One sentence, front-loaded with the verb and result, with no filler. The payload detail ('with session counts') is placed where it is immediately useful.

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 trivial single-parameter enumeration tool with full schema coverage and annotations, the description covers purpose, data scope, and return contents. The only gap is the absence of any pointer to which sibling consumes these years, which is minor at this complexity level.

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 description coverage is 100% and the single optional parameter ('format', enum markdown/json with a default) is fully documented in the schema. The description adds nothing about format selection, so the baseline of 3 applies.

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?

States a specific verb and resource ('Returns the set of WWDC years') and adds the payload detail ('with session counts'). It is clear what the tool produces, but it does not distinguish itself from nearby enumeration siblings such as wwdc_index_counts or wwdc_topics_by_year.

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?

Usage is only implied: an agent can infer this is a discovery call to find valid years before using wwdc_topics_by_year or wwdc_list_sessions. There is no explicit when-to-use, when-not-to-use, or named alternative, so the routing decision is left to inference.

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