Tunnel Manager

Send File

tm_inventory_send_file

Copies a local file to a specified remote path across hosts in a YAML inventory group, enabling bulk file distribution without manual per-host transfers.

Instructions

Send file (tm_inventory). Bulk inventory operations against YAML host groups.

Input Schema

Name	Required	Description	Default
`cfg`	No	Local SSH config path (copy_ssh_config).
`cmd`	No	Shell command (run_command).
`key`	No	Shared key path (configure_key_auth).	/app/.ssh/id_ed25519
`host`	No	run_command only. Optional single-host alias to target instead of the whole 'group' fan-out — the safe way to reach ONE inventory host (e.g. 'gb10') without running against 'homelab'. Resolved and authorized through the same alias store tm_remote/tm_hosts use, so the two are one source of truth: an unknown or unauthorized alias is rejected outright, never silently skipped. Takes precedence over 'group' when set.
`group`	No	Target group.	all
`lpath`	No	Local file path (send_file).
`rpath`	No	Remote file path (send_file/receive_file).
`key_pfx`	No	Prefix for new keys (rotate_key).	/root/.ssh/id_
`preview`	No	run_command only. If true, resolve the exact target host(s) for 'host'/'group' and return them in 'resolved_hosts' WITHOUT running 'cmd' — lets a caller verify scope before executing for real (no surprise fan-out). The real (non-preview) response also always includes 'resolved_hosts' for the same reason.
`rmt_cfg`	No	Remote config path (copy_ssh_config).	/root/.ssh/config
`timeout`	No	Command timeout in seconds.
`key_type`	No	Key type: rsa or ed25519.	ed25519
`parallel`	No	Run parallel.
`inventory`	No	YAML inventory path (default: $XDG_CONFIG_HOME/agent-connectors/inventory.yaml).	/root/.config/agent-connectors/inventory.yml
`max_threads`	No	Max threads.
`lpath_prefix`	No	Local dir prefix (receive_file).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.3.1Oct 21, 2026

TDQS

C2.6/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is partly covered. The description adds no behavioral context such as whether files are overwritten, what permissions are required, or how the inventory fan-out affects execution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only two short sentences and front-loads the action 'Send file'. The second sentence is generic but does provide inventory scope context, and there is no wasted filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a 16-parameter, open-world, non-idempotent inventory operation with many siblings, and the description gives almost no operational context. The schema and annotations cover structure and safety hints, but the description does not explain usage, alternatives, or file-transfer behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all 16 parameters are documented in the input schema. The description adds no parameter-level meaning beyond what the schema already provides, which matches the baseline of 3 when the schema carries parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description repeats the tool name/title with 'Send file (tm_inventory)' and adds a broad phrase about bulk inventory operations against YAML host groups. It does not clarify what sending a file entails, such as copying a local path to remote hosts selected from inventory, and it does not distinguish this from sibling tm_remote_send_file.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus tm_remote_send_file or tm_inventory_receive_file. The phrase 'Bulk inventory operations against YAML host groups' hints at inventory scope, but no conditions, exclusions, or alternatives are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server