use_connectionSwitch to a named MySQL connection profile immediately, with optional database override, without restarting the client.
Switch to a named connection profile. Takes effect immediately, no restart needed
| Name | Required | Description | Default |
|---|---|---|---|
| profile | Yes | Profile name from list_connections | |
| database | No | Optional database to use instead of the profile's own database |
Changes observed during successful MCP inspections.
v1.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context by stating 'Takes effect immediately, no restart needed', which is not covered by annotations. This clarifies the impact and side effects of switching profiles.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences with no wasted words. It front-loads the core purpose and immediately adds a key behavioral detail. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with two parameters and no output schema, the description covers the essential purpose and a critical behavioral trait. It lacks details about error handling or side effects on the current session, but given the annotation coverage and schema richness, it is reasonably complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both 'profile' and 'database' documented. The description adds no additional parameter information beyond what the schema provides, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Switch' and the resource 'named connection profile', making the tool's purpose unambiguous. It distinguishes from sibling tools like 'use_database' (switches database, not profile) and 'connect' (likely establishes a new connection rather than switching profiles).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives such as 'connect' or 'use_database'. It does not mention any conditions or exclusions, leaving the agent to infer the appropriate context from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.