Follow-up questions work without server-side memory: the host passes the previous turn as an optional context.previous parameter, so a terse "does it fire on update?" resolves against the component and tool from the previous answer.
Every area below maps to the full Salesforce MCP tool reference, and the Salesforce org intelligence use cases show these tools applied to real admin, developer and architect workflows.
› see all 209 tools - each explained
01 · find
Find & identify components
Locate an object, field, class or Flow even when you only half-remember its name. The resolver tolerates typos, filler words, and the org's own misspellings - and asks a clarifying question when several things match.
resolve · search_components · find_field_anywhere · find_semantic_field · get_component · list_components
- Where is the email field?
- What is the payment object actually called?
- Find the field that stores a social security number.
- Is there a class that handles refunds?
02 · understand
Understand what something does
Explain a single component in plain terms - a field's meaning, a Flow's logic, an Apex method, a formula, or everything that fires when a record is saved. For what a component structurally implies, interpret joins a curated, org-independent concept model (142 concepts / 193 rules) against your grounded graph and runs it as a deterministic rule engine over an offline slice, returning cited, confidence-tiered claims - never an LLM guess, never a live read.
explain_field · explain_flow · explain_apex_method · explain_formula · field_meaning · what_happens_on_save · interpret
- What does the Payment_Status__c field mean?
- Explain what this flow does.
- Is this field a formula or a roll-up - is it read-only?
- Do I have stacked record-triggered flows on this object?
03 · impact
Impact & dependencies
See what depends on a component and what would break before you change or delete it - the dependency graph plus what-if simulations. interpret adds the structural consequence: what happens to child records when a master-detail parent is deleted, why a roll-up field is read-only, or that an object's two master-detail parents make it a junction - each a cited claim, held no higher than the evidence beneath it.
get_impact · downstream_effects · get_edges · field_lineage · safe_to_delete_field · what_if_deactivate_flow · package_impact · interpret
- What breaks if I delete this field?
- What happens to child records if I delete this parent?
- Is it safe to deactivate this flow?
- What if I make this field required?
- What of mine breaks if I uninstall the SBQQ package?
04 · access
Permissions, sharing & access
Answer who-can-see-what and why - profile and permission-set grants, field-level security, and the record-visibility cascade.
why_cant_user_see_record · crud_fls_audit · field_access_audit · generate_sharing_summary · unassigned_permission_sets
- Why can't this user see this record?
- Who can edit the Salary field?
- Which permission sets are assigned to nobody?
- Summarize sharing for the Account object.
05 · automation
Automation & code behavior
Trace what runs and when - the order of execution on save, the Apex call graph, governor-limit risks, dead code, and test coverage.
order_of_execution · call_graph · governor_limit_risks · find_dead_code · test_coverage_for_method · tests_for_change · method_reachability
- What automation runs when a Case is created?
- Show the call graph for this Apex class.
- Which Apex methods have no real test coverage?
- Which tests should I run for the classes I changed?
- Where are the governor-limit risks?
06 · integration
Integrations & external systems
Map how the org talks to the outside world - named credentials, endpoints, outbound messages, and change-data-capture subscribers.
integration_map · endpoint_catalog · outbound_message_catalog · cdc_subscribers
- What external systems does this org talk to?
- List every outbound endpoint.
- Who subscribes to change events?
07 · docs
Generate documentation
Produce ready-to-share artifacts - an org tour, an admin handbook, an architecture overview, a data dictionary, or an onboarding doc. Each carries freshness frontmatter and per-section confidence labels.
org_overview · generate_admin_handbook · generate_architecture_overview · generate_data_dictionary · generate_onboarding_doc
- Give me a tour of this org.
- Generate an admin handbook.
- Build a data dictionary.
- Write an onboarding doc for a new developer.
08 · govern
Health, freshness & audit
Check the vault's freshness, see what changed recently, inventory PII, and score technical debt - the governance surface.
health_check · coverage_report · org_pulse · changed_since · trend · diff_snapshots · last_modified · pii_inventory · tech_debt_score · org_risk_report
- Is my vault up to date?
- What changed since last month?
- Where is PII stored in this org?
- How much technical debt is there?
09 · live · opt-in
Live org data opt-in
Read-only runtime facts from the connected org via the Salesforce CLI - counts, samples, field population, org limits. The default conversation stays offline; live tools never silently substitute a vault answer, and you grant consent once per org.
live_count · live_sample · live_describe · live_field_population · live_stale_records · live_recent_activity · live_aggregate · live_duplicate_check · live_owner_breakdown · live_storage_by_object · live_org_limits · live_inactive_users · live_permset_holders · live_user_permsets · live_group_members · live_zombie_accounts · live_license_usage · live_report_usage · live_org_health
- How many Accounts have Industry filled in?
- Sample 10 Opportunities in Negotiation.
- What are the current org governor limits?
- Which paid licenses are provisioned but unused?
- Who holds the Sales Manager permission set?
- What permission sets does Jane hold?
- Who is in the Support queue right now?
- Which active users have no permission-set assignments?
A map of what the knowledge base can answer, not a guarantee every tool applies to your org. Answers are only as fresh as your last refresh.
Ready to point it at your org?
Install takes one line, and the first refresh is read-only.