termix_hosts_bulk_import_ssh_hostsAdd multiple SSH hosts to Termix in one operation. Provide an array of host configurations to import them at once, simplifying setup.
Bulk import SSH hosts. Bulk imports multiple SSH hosts.
| Name | Required | Description | Default |
|---|---|---|---|
| hosts | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds only the word 'bulk' without disclosing whether existing hosts are overwritten, whether partial failures occur, or what validation is performed. With no idempotency hint and a bulk write, more behavioral disclosure is needed.
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 very short and front-loaded, but its only informative sentence is a near-verbatim repetition of the tool name. It is concise but not efficient, since it adds no new information.
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?
This is a bulk mutation tool with an untyped array parameter, no output schema, and 0% schema coverage. The description fails to explain the expected host object shape, failure behavior, or relationship to sibling host import/create tools, leaving an agent under-equipped to invoke it correctly.
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?
With schema coverage at 0%, the description carries full responsibility for explaining the 'hosts' array parameter. It does not describe the expected fields of each host object, required properties, or matching logic. The parameter name 'hosts' gives limited inherent meaning, so a low-middle score 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 states the verb and resource ('Bulk import SSH hosts') but essentially repeats the tool name. It does not meaningfully differentiate this tool from siblings like termix_hosts_import_hosts_openssh_config_file or termix_hosts_create_ssh_host.
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?
No guidance on when to use this tool versus alternatives. It does not mention the sibling OpensSH config import tool, single-host create/update tools, prerequisites, duplicate handling, or batch failure semantics.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.