Skip to main content
Glama

Federated search across all Apple content

apple_search_all
Read-onlyIdempotent

Search WWDC sessions, Apple docs, Human Interface Guidelines, and Swift Evolution together, then get merged results ranked by relevance for source-grounded Apple development answers.

Instructions

Search all indexed Apple content at once: WWDC sessions, Apple docs, HIG, and Swift Evolution. Results are merged and ranked by relevance.

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": {
      "query": "<query>"
    },
    "name": "apple_search_all"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesSearch query
typesNoContent types to include
formatNoResponse formatmarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / query / maxLength
      Added value: +500
  2. First observedv0.2.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description still adds real behavioral value beyond that: results are merged across corpora and ranked by relevance, which tells the agent the output is a single interleaved list rather than per-source blocks. It stops short of disclosing latency, per-type result allocation, or whether 'limit' is total or per type.

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 scope enumeration and followed by the ranking/merge behavior. Every clause carries information; there is no restatement of the name or filler.

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?

With no output schema, the description should convey more about what comes back from a federated query — whether results are homogeneous across corpora, whether 'limit' caps the merged list or each source, and whether the ranking interleaves types. The merge/rank sentence is genuinely useful but leaves meaningful gaps for a 4-parameter aggregation tool.

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 75%: query, types and format are documented in-schema, while limit relies on its default (15) and min/max bounds. The description adds nothing about parameter behavior — notably it never explains that the four named corpora correspond to the optional 'types' filter, which would have been the highest-value clarification available. Baseline 3 is appropriate when the schema already carries most of the load.

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?

States a specific verb ('Search') plus an explicit resource enumeration (WWDC sessions, Apple docs, HIG, Swift Evolution) and the scope qualifier 'all ... at once'. Because it names exactly the four corpora that the single-corpus siblings (wwdc_search, apple_hig_search, apple_swift_evolution_list, apple_doc_lookup) cover individually, an agent can tell this is the federated entry point without opening any schema.

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?

'at once' and 'all indexed Apple content' imply the broad-discovery use case, so the when-to-use is inferable. However, there is no explicit routing guidance: nothing says to prefer this over wwdc_search when only WWDC content is wanted, or that per-corpus tools return deeper results. No exclusions or prerequisites are stated.

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