Skip to main content
Glama

Read full WWDC session transcript in chunks

wwdc_session_transcript_full
Read-onlyIdempotent

Retrieve complete WWDC session transcripts in paginated chunks when a session excerpt is insufficient, starting at chunk 0 and incrementing to totalChunks.

Instructions

Retrieve the complete transcript of a WWDC session in paginated chunks. Use chunk_index=0 to start, then increment until chunk_index >= totalChunks. Useful for sessions where the excerpt in wwdc_get_session is insufficient.

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

Input Schema

NameRequiredDescriptionDefault
idYesSession ID, e.g. wwdc2024-10150.
formatNoResponse formatmarkdown
chunk_sizeNoCharacters per chunk (default 8000, max 20000).
chunk_indexNo0-based chunk index.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety needs no restating. The description adds real behavioral value beyond that: it explains the chunking model and the iteration protocol with a termination condition. It does not say where totalChunks is surfaced in the response or whether chunk boundaries can shift if chunk_size changes, which is a minor remaining gap.

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?

Three short sentences with zero waste: purpose first, iteration protocol second, selection guidance last. Every sentence carries information an agent needs, and the pagination instruction is placed before the sibling comparison.

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?

There is no output schema, so the description carries the burden of describing returns; it partially does so by naming totalChunks as part of the response model, but never states what a chunk actually contains (text plus index/metadata). For a 4-parameter paginated read tool with full annotation coverage, this is nearly complete with one modest documentation gap.

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 coverage is 100%, so the baseline is 3, but the description goes further by prescribing how chunk_index is actually used: start at 0 and increment until chunk_index >= totalChunks. That is usage meaning not encoded in the schema. It still doesn't explain how chunk_size interacts with the returned totalChunks or which format yields which chunk payload.

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

Purpose5/5

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

States a specific verb and resource ('Retrieve the complete transcript of a WWDC session') plus the delivery mode ('paginated chunks'), and explicitly separates itself from wwdc_get_session by framing this as the full-text path when the excerpt is insufficient. An agent can distinguish it from siblings like wwdc_transcript_search or wwdc_session_summary without opening a schema.

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?

Gives a concrete selection condition and names the alternative: use this when 'the excerpt in wwdc_get_session is insufficient.' There are no explicit when-not cases (e.g., for targeted keyword lookups that wwdc_transcript_search handles better), so it stops short of full routing guidance.

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