Skip to main content
Glama

Apple API availability (min OS version)

apple_api_availability
Read-onlyIdempotent

Look up the minimum OS version an Apple API was introduced in and check whether it has been deprecated, using Apple documentation data.

Instructions

Look up the minimum OS version an Apple API was introduced in, and whether it has been deprecated. Uses the apple_docs index.

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

Input Schema

NameRequiredDescriptionDefault
formatNoResponse formatmarkdown
api_nameYesSymbol name, e.g. "SwiftUI.View", "UITableView"

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds one piece of genuine context beyond the structured fields: it draws from the apple_docs index, which tells the agent this is a bounded, closed-world lookup. It does not say what happens when the API is not found or how deprecation is signalled in the response.

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, front-loaded with the capability and followed by the data source. No filler, no restatement of the tool name or title, and nothing that could be trimmed without losing information.

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?

The tool is simple (one required string parameter plus a response-format toggle) with full schema coverage and rich annotations, so the description carries proportionally little burden. Telling the agent the answer comes from the apple_docs index is the key completeness detail; only the not-found behaviour is left unstated, and there is no output schema to clarify it.

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% and both parameters are documented in the schema, including a format enum with a default and a concrete example for api_name. The description adds no parameter meaning beyond that, so the baseline of 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?

The description names a specific verb and resource pair ("look up the minimum OS version an Apple API was introduced in") plus a second capability (deprecation status), so the purpose is unambiguous. It falls short of 5 because it does not distinguish itself from closely overlapping siblings such as apple_api_deprecation and wwdc_find_api_introduction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. Given that the sibling list contains at least three tools that sound like they answer overlapping questions (apple_api_deprecation, wwdc_find_api_introduction, apple_what_replaced), the absence of routing guidance is a real gap.

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