termix_files_stream_download_fileStream-download a file as binary data over SFTP or SCP legacy. Retrieves remote file content directly for transfer or processing.
Stream-download a file. Downloads a file as a binary stream. Uses SCP legacy mode (cat over exec) when the host has scpLegacy enabled, otherwise uses SFTP.
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | ||
| sessionId | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. The description adds the transport detail (SCP legacy vs SFTP) which is useful behavioral context beyond annotations. However, it doesn't disclose what happens with the binary stream, whether the session must be established first, or any side effects.
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 sentences with no waste. The core action is front-loaded, and the transport detail is a useful addition. It 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 tool with 2 parameters, 0% schema coverage, no output schema, and no parameter descriptions, the description is too thin. An agent doesn't know what sessionId refers to, whether a session must be pre-established, what the binary stream output looks like, or how this differs from termix_files_download_file. The transport detail helps but doesn't fill the gaps.
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 0%, so the description must compensate for the two parameters (path, sessionId). The description mentions 'file' and 'host' implicitly but doesn't explain what path or sessionId mean, their format, or how they relate. This is a significant gap given zero schema coverage.
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 a specific verb and resource: 'Stream-download a file. Downloads a file as a binary stream.' This clearly identifies the operation. It doesn't explicitly distinguish from sibling termix_files_download_file, but the 'stream' qualifier in the name and description provides some differentiation.
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 mentions the transport mechanism (SCP legacy mode vs SFTP) which implies when it might be used, but doesn't explicitly state when to use this tool vs alternatives like termix_files_download_file. No exclusions or alternative tool names are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.