Skip to main content
Glama
synology-mcp
by r03eRt

Drive: file details

drive_get_info
Read-only

Retrieve detailed metadata for a Synology Drive file or folder by path, ID, or link, including size, owner, labels, star status, sharing state, file ID, and permanent link.

Instructions

Details of one Drive file or folder: size, owner, labels, star, sharing state, file_id and permanent link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "drive_get_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesDrive path: "/mydrive/<path>" (the user's My Drive = /home/Drive in File Station), "/team-folders/<name>/<path>", "id:<file_id>" or "link:<permanent_link>"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this a safe, non-open-world read, so the description's remaining burden is low. It adds the returned field set (size, owner, labels, star, sharing state, file_id, permanent link), which is real value since no output schema exists, but it says nothing about error behavior for an unresolved path or permission requirements on team folders.

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

Conciseness5/5

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

A single sentence with the resource and scope front-loaded and the attribute list packed efficiently after the colon. Nothing is redundant and no sentence is wasted.

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

Completeness4/5

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

For a one-parameter read tool with no output schema, the description covers the resource and the shape of the return value, which is the main informational gap. Only failure modes and team-folder permission nuances are left unaddressed, which is a minor omission at this complexity.

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 coverage is 100% and the path property already documents all four accepted forms ('/mydrive/...', '/team-folders/...', 'id:<file_id>', 'link:<permanent_link>'). The description's mention of file_id and permanent link loosely echoes two of those forms but adds no syntax detail beyond the schema, so the baseline 3 applies.

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

Purpose4/5

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

The description names a specific resource and scope ('Details of one Drive file or folder') and enumerates the returned attributes, so the agent knows this is a single-item metadata lookup rather than a listing. It does not name which sibling to use instead (e.g. drive_list or get_file_info), but the singular scope is clear enough to differentiate.

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

Usage Guidelines3/5

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

Usage is only implied: 'one Drive file or folder' signals single-item lookup versus the drive_list family, but there is no explicit when-to-use, when-not-to-use, or alternative named. An agent must infer the routing from scope wording alone.

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