Skip to main content
Glama

Get WWDC session

wwdc_get_session
Read-onlyIdempotent

Retrieve a WWDC session record by ID with topics, transcript, sample-code URLs, and related docs to ground Apple developer research.

Instructions

Full record for a WWDC session by id (e.g. wwdc2024-10150). Includes description, topics, transcript, sample-code URLs, related docs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "wwdc_get_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSession id, e.g. wwdc2024-10150
formatNoResponse formatmarkdown
include_chaptersNo
include_judgmentNo
transcript_charsNoMaximum transcript characters to return in markdown/json when transcript is included.
include_transcriptNo
include_sample_codeNo
include_related_docsNo

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description adds payload-level context by enumerating what the record contains (topics, transcript, sample-code URLs, related docs), which is genuinely useful. It does not, however, disclose that the transcript is truncated by default (transcript_chars default 8000, max 25000) or how the response is shaped in markdown vs json.

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 short sentences, front-loaded with the verb+resource and the required identifier, then a compact enumeration of returned content. No filler, no restatement of the title.

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 8 parameters, no output schema, and low schema coverage, the description should carry more weight. It covers what is returned but not the toggles that materially change the payload (chapter inclusion, judgment, transcript length cap) or the format switch, so an agent cannot predict response size or shape from the description alone.

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

Parameters4/5

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

Schema description coverage is only 38% (5 of 8 params have no description), so the description must compensate. It does partially by naming the payload components that map to include_transcript, include_sample_code and include_related_docs, and by repeating the id format. It leaves format, include_chapters, include_judgment and transcript_chars unexplained, so compensation is incomplete.

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 ('Full record for a WWDC session by id') and gives a concrete id example, so the agent knows exactly what it retrieves. The word 'Full' implicitly contrasts with the summary/transcript siblings, but no sibling is named, so differentiation is left to inference.

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: the tool requires a session id, which suggests it belongs downstream of a search/list tool, but the description never says so or names wwdc_search / wwdc_list_sessions as the id source. There are no when-not-to-use notes versus wwdc_session_summary, wwdc_session_transcript_full, or wwdc_session_deep_link.

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