Skip to main content
Glama

What replaced a deprecated Apple API

apple_what_replaced
Read-onlyIdempotent

Find what replaced a deprecated Apple API by symbol and list WWDC sessions that introduce the replacement.

Instructions

Given a deprecated Apple API symbol, finds what replaced it (from the deprecated_message field) and lists WWDC sessions introducing the replacement.

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": {
      "api_name": "<api_name>"
    },
    "name": "apple_what_replaced"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoResponse formatmarkdown
api_nameYesDeprecated API name, e.g. "UIWebView", "UIAlertView"

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

A4/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context by naming the data source ('deprecated_message field') and disclosing that results include WWDC session introductions — useful composition detail given there is no output schema. It stays silent on the no-replacement-found case.

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?

A single sentence, front-loaded with the input precondition and immediately followed by both output components. No filler, no restatement of the tool name.

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 two-parameter lookup with no output schema, the description carries enough: input precondition, where the replacement comes from, and the extra WWDC payload. It could be complete with one more clause on behavior when no replacement is recorded or on what the 'format' parameter changes.

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%, with api_name already documented as a deprecated API name with examples like UIWebView. The description restates that it expects a deprecated symbol but adds no format hints, matching patterns, or guidance on the untouched 'format' enum parameter. Baseline 3 applies when the schema does the heavy lifting.

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?

The description states a specific transformation: given a deprecated API symbol, return its replacement plus the WWDC sessions that introduced it. That distinguishes it in intent from siblings like apple_api_deprecation and wwdc_find_api_introduction, though it never names those siblings, so the differentiation is inferential rather than explicit.

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 opening clause 'Given a deprecated Apple API symbol' acts as a clear usage trigger: reach for this when you already have a deprecated symbol and need a migration path. It does not state when *not* to use it or point at an alternative tool for the 'is this deprecated?' question, which is the main gap.

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