Skip to main content
Glama

Find when an Apple API was introduced

wwdc_find_api_introduction
Read-onlyIdempotent

Finds when a Swift symbol, framework, or feature first appeared in WWDC sessions and returns matches sorted by year so the earliest introduction is clear.

Instructions

Given a Swift symbol, framework, or feature name (e.g. 'SystemLanguageModel', 'SwiftData', '@Observable', 'LiquidGlass'), searches WWDC sessions to determine which year it was first announced or introduced. Returns sessions sorted by year ascending so the earliest hit is listed first.

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": {
      "symbol": "<symbol>"
    },
    "name": "wwdc_find_api_introduction"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
formatNoResponse formatmarkdown
symbolYesSwift symbol, API name, framework, or feature to find (e.g. 'SystemLanguageModel', 'SwiftData', 'LiquidGlass', '@Observable').

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral detail: the search is scoped to WWDC sessions and results are sorted by year ascending with the earliest hit first, which tells the agent how to read the response. It omits caveats such as what happens when nothing matches or that pre-WWDC APIs will not be found.

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?

Two tight sentences, front-loaded with the purpose and followed by the return-ordering rule. The parenthetical example list is somewhat redundant with the symbol parameter description, but it is short and aids pattern matching.

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 carries the burden of return shape and does so at a high level ('returns sessions sorted by year ascending'). For a simple three-parameter lookup tool this is nearly complete; only the empty-result case and the markdown-vs-json difference are left unstated.

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 67%: 'symbol' and 'format' are documented in the schema, and the description's symbol examples largely duplicate the schema text. The 'limit' parameter has bounds and a default but no described meaning in either place, and the description does not explain how limit interacts with the year-ascending sort. Baseline 3 is appropriate.

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: 'searches WWDC sessions to determine which year it was first announced or introduced'. The examples ('SystemLanguageModel', 'SwiftData', '@Observable') make the input domain concrete. It does not explicitly name the nearest sibling (wwdc_sessions_for_api) to draw the boundary, so an agent must infer the difference between 'when was this introduced' and 'which sessions cover this API'.

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 by the phrasing 'Given a Swift symbol, framework, or feature name... determine which year it was first announced'. There is no explicit when-to-use versus when-not, and no pointer to alternatives like apple_api_availability or wwdc_sessions_for_api for follow-up questions.

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