Skip to main content
Glama

WWDC topics by year

wwdc_topics_by_year
Read-onlyIdempotent

Find popular WWDC session topics for a given year or compare topic frequency trends across years.

Instructions

Show the most popular WWDC session topics for a given year, or a cross-year comparison table. Useful for 'what was hot at WWDC 2024?' or comparing topic frequency trends.

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

Input Schema

NameRequiredDescriptionDefault
yearNoWWDC year (e.g. 2024). Omit for a cross-year comparison table.
limitNoTop N topics to return per year.
formatNoResponse formatmarkdown

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this as a safe, idempotent, closed-world read, so the safety profile needs no restatement. The description adds value the annotations cannot: it discloses the shape of the result (a ranked 'most popular' list for one year, or a cross-year comparison table when year is omitted), which matters because 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?

Two tight sentences: the capability and its two modes come first, and the example phrasings follow as supporting context. Nothing is repeated from the schema and there is no filler.

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 3-parameter, zero-required, read-only aggregation tool with full schema coverage, this is essentially complete. The one unanswered question is how 'popular' is computed (frequency of mentions? topic counts?), which an agent might want in order to interpret the output.

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 100%, and the schemas themselves already document year (including the omit-for-comparison behavior), the 1-50 limit for top N per year, and the markdown/json format enum. The description adds only marginal framing ('most popular') on top of that, so baseline 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 ('Show the most popular WWDC session topics') and adds the cross-year comparison mode when the year is omitted. What it does not do is name or distinguish itself from the closely adjacent sibling wwdc_list_topics, leaving the agent to infer the difference.

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?

The quoted example questions ('what was hot at WWDC 2024?' and 'comparing topic frequency trends') give concrete use contexts that map cleanly onto the two modes. There are no explicit exclusions or comparative guidance versus wwdc_list_topics or wwdc_sessions_for_api, so it stops short of a 5.

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