Connections · stop 7 of 12
resolve_target
Picks the right connection from a hint like "staging" or a table name.
Works in read modeTool sets: query · full
You might ask
“Check the orders table in staging.”
Your assistant may call resolve_target to answer.
How it works
- Matches the hint against profile names, hosts, databases and indexed tables across all connections.
- If one match is clearly best it switches to it; if several fit equally it returns them and the assistant should ask you.
Parameters
hintstring- Free-text hint about the target connection: database name, environment, or host fragment.
objectHintstring- Free-text hint about a table/view name expected to live in the target database.
What your assistant reads
The description nexql-mcp sends with the tool. It's how the assistant decides when to use it.
Autonomously find which connection/database matches a user's hint (a database name, environment, host fragment) and/or an object hint (a table/view name), searching across ALL configured connections and their indexed schemas. Use it when the request names a database, environment, or object outside the current session context. When the match is unambiguous it switches the session context automatically and returns the resolved connection/database; only returns `ambiguous: true` with a candidate list when multiple equally-plausible matches exist, in which case surface those candidates to the user rather than guessing.