Skip to main content
Glama

LLM-generated session summary

wwdc_session_summary
Read-onlyIdempotent

Returns an AI-generated structured WWDC session summary with key APIs, topics, code patterns, and difficulty to help assess technical content; falls back to the session description if missing.

Instructions

Returns the AI-generated structured summary for a WWDC session: 2-3 sentence overview, key APIs, topics, code patterns, and difficulty level. Falls back to the session description if no summary has been generated yet. Run npm run ingest -- --source session-summaries to populate.

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": {
      "session_id": "<session_id>"
    },
    "name": "wwdc_session_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoResponse formatmarkdown
session_idYesSession ID, e.g. 'wwdc2024-10016'. Use wwdc_search or wwdc_get_session to find IDs.

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

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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: the graceful fallback to the session description when no AI summary exists, plus the exact ingest command needed to populate the data. The one gap is that it doesn't say how to tell from the response whether you got the fallback or a real summary.

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, front-loaded with what is returned, then the fallback caveat, then the operational fix. Every sentence carries information; the npm ingest command is developer-facing but earns its place by explaining how to resolve the empty-summary case.

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?

With no output schema, the description correctly compensates by listing the summary's fields, and it covers the main failure mode (no summary generated). It stops short of describing the response envelope (e.g. whether fallback content is flagged), which would fully close the loop for a read tool with a conditional return.

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% — session_id's format and how to discover IDs, plus the format enum, are already documented in the schema. The description adds no parameter-level meaning beyond that, so the 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?

"Returns the AI-generated structured summary for a WWDC session" is a specific verb+resource, and the enumeration (overview, key APIs, topics, code patterns, difficulty) makes the output shape unmistakable. It doesn't explicitly contrast with wwdc_get_session or wwdc_session_transcript_full, so sibling differentiation is left implicit.

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 implied rather than stated: an agent can infer this is the lightweight summary endpoint versus the full session/transcript tools, and the fallback sentence tells it what happens when no summary exists. There is no explicit "use X instead when you need Y" routing, which matters given how many sibling tools return session data.

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