Practical examples for using GliderMCP with a coding agent. Each one starts with a real C# task, then asks the agent to gather structured facts before editing.
Ask
> Load this solution, find the entry points for the checkout flow, then trace the controllers, handlers, services, validators, repositories, DTOs, and tests involved. Summarize the flow before proposing edits.
Why it helps
C# features often cross layers. GliderMCP helps the agent map relationships before it starts opening random files.
Tools: load, search_symbols, find_callers, get_outgoing_calls, get_type_info
Ask
> Before changing UserValidator, find its references, callers, and likely impact across the solution. Summarize the risky areas first.
Why it helps
Shared validators, services, and extension methods are easy for agents to change too broadly. Impact analysis makes the blast radius visible.
Tools: resolve_symbol, find_references, find_callers, analyze_change_impact
Ask
> Resolve CustomerService, preview renaming it to AccountService, and show the diff without applying it. Only apply the rename after diagnostics still look reasonable.
Why it helps
Preview-first refactoring keeps the agent from doing broad text replacement where symbol identity matters.
Tools: resolve_symbol, rename_symbol, get_diagnostics
Ask
> Resolve IPaymentGateway, find its implementations, then show which implementation is used by the checkout path.
Why it helps
Interfaces, dependency injection, and tests can make text search noisy. The agent needs actual implementations, not every matching word.
Tools: resolve_symbol, find_implementations, find_references, get_type_info
Ask
> Run diagnostics, group the biggest hotspots, then inspect the top failing files and propose the smallest fix plan.
Why it helps
Diagnostics give the agent a fast feedback loop and a concrete way to verify edits.
Tools: get_diagnostics, diagnostic_hotspots, get_file_contents
Ask
> Find likely-unused private symbols, unused parameters, and removable direct project references. Summarize safe cleanup candidates before editing.
Why it helps
Cleanup work needs caution around reflection, public APIs, and project boundaries. GliderMCP helps the agent gather evidence first.
Tools: find_unused_symbols, find_unused_parameters, find_unused_project_references
Ask
> Show the external definition for JsonSerializer.Serialize, then find where System.Text.Json is used in this solution.
Why it helps
Agents often need framework or package details to make correct API calls without pasting whole packages into context.
Tools: view_external_definition, find_package_usages
Ask
> Use bounded structure and symbol tools to inspect only the files needed for this bug. Avoid dumping whole files unless a specific line range is required.
Why it helps
Structured, bounded results keep the conversation focused on relevant C# relationships instead of giant file dumps.
Tools: get_structure, get_symbol_info, get_file_contents, batch