Search-Apple-Docs

search_framework_symbols

search_framework_symbols

Search symbols within Apple frameworks to explore APIs, find views, controllers, delegates, and discover available types for development.

Instructions

Browse and search symbols within a specific Apple framework. Perfect for exploring framework APIs, finding all views/controllers/delegates in a framework, or discovering available types. Use after list_technologies to get framework identifiers.

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": {
      "framework": "<framework>"
    },
    "name": "search_framework_symbols"
  }
}

Input Schema

Name	Required	Description	Default
`framework`	Yes
`symbolType`	No
`namePattern`	No
`language`	No
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 31, 2025

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the tool's function ('browse and search symbols') and scope ('within a specific Apple framework'), but lacks details on behavioral traits such as pagination, rate limits, authentication needs, or error handling. However, it does add context about the prerequisite (list_technologies), which is valuable.

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?

The description is appropriately sized and front-loaded, with two sentences that efficiently convey purpose and usage guidelines. Every sentence earns its place: the first defines the tool's function and use cases, and the second provides critical workflow context.

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?

Given the complexity (5 parameters, no annotations, no output schema), the description is incomplete. It covers purpose and usage well but lacks parameter explanations and behavioral details. However, it does provide essential context (prerequisite with list_technologies), making it minimally adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for all 5 parameters. It only mentions 'framework' implicitly (via 'specific Apple framework') and does not explain the semantics of symbolType, namePattern, language, or limit. This leaves most parameters undocumented, failing to add meaningful value beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('browse and search symbols') and resource ('within a specific Apple framework'), distinguishing it from siblings like list_technologies (which lists frameworks) and search_apple_docs (which searches documentation). It explicitly mentions exploring APIs, finding views/controllers/delegates, and discovering types, providing concrete use cases.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool: 'Use after list_technologies to get framework identifiers.' This clearly indicates a prerequisite and workflow context, helping the agent understand the proper sequence and alternative tools (e.g., use list_technologies first).

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

Deploy Server