Skip to main content
Glama

Apple API deprecation status

apple_api_deprecation
Read-onlyIdempotent

Check whether an Apple API symbol is deprecated, determine when it was deprecated, and identify its replacement to plan code updates.

Instructions

Check whether an Apple API symbol is deprecated, when it was deprecated, and what replaced it. Looks up by symbol name (e.g. UIWebView, UIAlertView).

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

Input Schema

NameRequiredDescriptionDefault
formatNoResponse formatmarkdown
api_nameYesSymbol name to look up, 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

A3.7/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 fully covered. Because there is no output schema, the description earns credit for disclosing the three pieces of information returned (status, deprecation timing, replacement symbol). It stops short of saying what happens for an unknown or non-deprecated symbol, or how complete the underlying symbol index is.

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 with no filler; the primary capability is stated first and the lookup key plus examples follow immediately. Nothing would be lost by keeping it exactly as is.

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?

For a two-parameter read-only lookup with full annotation coverage and no output schema, the description covers the essentials of what is returned. It leaves gaps around negative results, index scope, and how this differs from the closely related availability and replacement tools, which matters given the crowded sibling set.

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 100% and both parameters already carry descriptions, including the enum for format, so the schema does the heavy lifting. The description's mention of symbol-name lookup and its UIWebView/UIAlertView examples restate the api_name field rather than adding new meaning, which is the baseline 3 case.

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 concrete verb and outcome: checks whether a symbol is deprecated, when, and what replaced it, with example symbols. That is specific enough to act on, but the description never distinguishes this tool from sibling lookups like apple_api_availability or apple_what_replaced, which appear to overlap with parts of the stated purpose.

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 and the concrete symbol examples, so an agent can infer this is the deprecation-lookup entry point. However, there is no explicit when-to-use framing, no conditions or prerequisites, and no mention of the alternative tools an agent should pick for availability-versus-replacement questions.

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