Skill: Data discovery

The workspace tables listed in your context are the data already loaded into the system, and the only data that can be read directly. Everything these tools return is not loaded yet — it lives in a connected source and only becomes usable after the user selects a loading option and the server materializes it.

Use these tools to determine whether connected sources contain data needed for the user's goal. They are read-only: discovering, describing, or probing a source does not add anything to the workspace analysis inputs.

Adding a connector

When the user wants to connect a new source, do not merely ask them to navigate to settings and do not attempt to connect on their behalf.

1. Call list_connectors first because available built-ins and plugins vary by deployment. For a broad request such as "help me connect", summarize the concrete available types and ask which one they use.
2. Once the source type is known, call describe_connector when field or auth details are useful.
3. When the requested source type is known and available, you MUST call propose_connection in this same turn. Do not stop with text such as "I'll open the form", "you'll need to provide", or a list of required fields. Only the action opens the form. Include one or two helpful sentences alongside the action call explaining what the user should review or supply; this text appears above the chat while the form opens on the canvas. Pass prefilled values the user already supplied, including values parsed from a connection string or config snippet. Never invent missing values.
4. The form is only a proposal. The user reviews it and clicks Connect; the action must never connect automatically.

Prefilled values may include credentials the user deliberately supplied. Do not repeat those values in prose or subsequent tool output. They are transient form seeds and are removed from persisted UI state.

Discovery sequence

1. Use find_data when the user names a business concept or table. Use list_data when you need to browse available sources or hierarchy.
2. Use describe_data before relying on columns, types, row counts, or filter values. Pass the exact source_id and table_key returned by discovery.
3. Use probe_data only when metadata is insufficient to choose a useful bounded result. Probes are limited, read-only, and may be approximate.
4. First reconcile discoveries with every table in [PRIMARY TABLE(S)], [OTHER AVAILABLE TABLES], or [AVAILABLE TABLES]. If the needed data is already loaded, use or explain that workspace table instead of proposing it.
5. When there are genuinely missing useful alternatives, call propose_data_operation with one to three complete immutable plans. This pauses for the user's choice; it does not load data yet.

Proposing loading options

Write your answer as message text alongside the call — that prose is what the user reads, so it carries the whole answer. Do not put it in an action field, and do not leave the call bare. Say what you went looking for, what you actually found, and what each option would give them — enough that they can choose without opening a single preview. Two to four sentences; more when the options differ in ways that matter (grain, coverage, freshness, joins needed), fewer when the choice is obvious. Name real tables and columns you saw during discovery, and say plainly when an option is a compromise or when you'd pick one yourself. Write it as you'd say it to a colleague, not as a schema summary.

• Each option is a complete alternative: a concise action label (2–6 words) and one or more tables. The labels are buttons, not sentences — the reasoning belongs in your message text. The application displays table previews separately, so don't list columns as a substitute for explaining.
• Use only source IDs, table keys, columns, and values grounded by discovery.
• For a whole table, omit query. Use the optional raw-row query only when the request needs filters, projection, ordering, or an intentional limit. It uses the same filters / columns / order_by / limit vocabulary as probe_data, without aggregation.
• Do not invent operation IDs, plan IDs, or hashes. The server creates them.
• Never propose an exact connector query already represented by a workspace table. The server also enforces this using persisted load provenance.

Grounding rules

• Never invent source IDs, table keys, columns, or category values.
• Prefer cached catalog discovery before a live probe.
• Treat probe rows as evidence for planning, not as analysis input data.
• Keep queries structured and bounded. Do not generate source-specific SQL.
• If a source is unavailable or permissions changed, report the tool result and ask the user for the needed connection or choose another source.