memorydetective

Overview Schema Source Related Servers Discussions Admin

List top-level symbols in a Swift file

swiftGetSymbolsOverview

Retrieve top-level symbols (classes, structs, enums, protocols, functions) from a Swift file to quickly orient yourself after navigating to a new file.

Instructions

[mg.code] Cheap orientation: returns the top-level symbols (classes, structs, enums, protocols, free functions) declared in a Swift file via SourceKit-LSP's documentSymbol. Set topLevelOnly: false for nested children too. Useful right after swiftGetSymbolDefinition lands you in a new file.

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": {
      "filePath": "<filePath>"
    },
    "name": "swiftGetSymbolsOverview"
  }
}

Input Schema

Name	Required	Description
`filePath`	Yes	Absolute path to a Swift source file.
`projectRoot`	No
`topLevelOnly`	No	Return only top-level symbols (classes, structs, enums, protocols, free functions). When false, returns nested children too. Default true keeps responses small.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.7.0May 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Describes as 'cheap orientation' via SourceKit-LSP's documentSymbol, implying a read-only, lightweight operation. No annotations to contradict; clear enough for agent to infer safety.

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 concise sentences, front-loaded with purpose and key parameter guidance. No redundant or irrelevant information.

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?

Covers purpose and usage context well, but lacks description of return format (symbol structure) despite no output schema. Relies on prior knowledge of documentSymbol output.

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?

Adds value for topLevelOnly by explaining its effect and default behavior. But projectRoot lacks description in both schema and tool description, and filePath is covered identically in 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?

Description clearly states verb (returns), resource (top-level symbols in Swift file), and distinguishes from sibling swiftGetSymbolDefinition by noting it gives orientation after landing in a new file.

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?

Explicitly suggests using after swiftGetSymbolDefinition for quick orientation, and hints at topLevelOnly parameter adjustment. Does not exclude other cases or compare with other swift tools.

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