Skip to main content
Glama

Receive File

tm_inventory_receive_file

Receive files in bulk from hosts defined in YAML inventory groups. Copies remote files to a local directory prefix, with optional single-host targeting and parallel transfers.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tm_inventory_receive_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
cfgNoLocal SSH config path (copy_ssh_config).
cmdNoShell command (run_command).
keyNoShared key path (configure_key_auth)./app/.ssh/id_ed25519
hostNorun_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.
groupNoTarget group.all
lpathNoLocal file path (send_file).
rpathNoRemote file path (send_file/receive_file).
key_pfxNoPrefix for new keys (rotate_key)./root/.ssh/id_
previewNorun_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_cfgNoRemote config path (copy_ssh_config)./root/.ssh/config
timeoutNoCommand timeout in seconds.
key_typeNoKey type: rsa or ed25519.ed25519
parallelNoRun parallel.
inventoryNoYAML inventory path (default: $XDG_CONFIG_HOME/scion-sdk/inventory.yml)./root/.config/scion-sdk/inventory.yml
max_threadsNoMax threads.
lpath_prefixNoLocal dir prefix (receive_file).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.4.7
    • changedInput schema / properties / inventory / default
      Previous value: -"/root/.config/agent-connectors/inventory.yml"New value: +"/root/.config/scion-sdk/inventory.yml"
    • changedInput schema / properties / inventory / description
      Previous value: -"YAML inventory path (default: $XDG_CONFIG_HOME/agent-connectors/inventory.yaml)."New value: +"YAML inventory path (default: $XDG_CONFIG_HOME/scion-sdk/inventory.yml)."
  2. Addedv3.3.1

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false, so the description should add what non-idempotent receiving actually does (overwrite behavior, target directory semantics, auth requirements). It adds none of that; the only added phrase describes a different class of operations entirely.

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

Conciseness2/5

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

It is short, but the second sentence does not earn its place: it is off-topic for a receive operation and actively misleads about scope. Front-loading is spent repeating the title rather than stating the action.

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?

For a 16-parameter, zero-required, non-idempotent mutation tool that fans out across inventory groups, the description supplies almost none of the context an agent needs — no direction of transfer, no required inputs by operation, no fan-out or overwrite caveats. An output schema exists, so return values need not be explained, but that is the only burden lifted.

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% and each of the 16 parameters already carries an inline hint, so the baseline applies. The description contributes no additional meaning about which parameters matter for receiving (rpath, lpath_prefix, host/group, parallel, max_threads) or how defaults combine.

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

Purpose2/5

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

The description opens with a restatement of the title ("Receive file") and then appends "Bulk inventory operations against YAML host groups," which describes the whole inventory family rather than this operation and never says what is received, from where, or into which local path. With ~25 siblings including tm_remote_receive_file and tm_inventory_send_file, nothing distinguishes this tool's specific scope.

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?

No when-to-use or when-not-to-use guidance is given, and the closest alternative (tm_remote_receive_file) is neither named nor contrasted, nor is the relationship to tm_inventory_send_file or tm_inventory_run_command explained. An agent has to infer everything from the sibling list.

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