Returns metadata for a single remote file or directory by its absolute path within a JumpServer SFTP session. Use when you need to check file existence, size, or modification time before performing transfers or deletions.
Return metadata for one absolute remote path.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| session_handle | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. 'Return metadata' suggests a read-only operation, but it does not disclose error behavior, symlink handling, or permission requirements. The mention of 'absolute' adds some useful context.
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?
A single, front-loaded sentence with no filler. It efficiently communicates the tool's core purpose.
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?
Given the tool's simplicity and the presence of an output schema, the description is mostly complete. It could be improved by mentioning the need for an active SFTP session, but overall it provides enough context for a straightforward stat operation.
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?
The description adds meaning to the 'path' parameter by specifying it must be an 'absolute remote path'. However, 'session_handle' is only explained by its schema title, and with 0% schema coverage, the description only partially compensates.
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 uses a specific verb 'Return' and identifies the resource as 'metadata for one absolute remote path', clearly distinguishing it from sibling tools like jms_sftp_list which lists directory contents.
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?
Usage is implied: use this tool to get metadata for a single remote path. However, it does not explicitly state when to prefer this over alternatives, nor does it provide exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.