Skip to main content
Glama
Sign In
synology-office-mcp

synology-office-mcp

by vocweb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

drive_get_file_info

Retrieve comprehensive metadata including size, owner, ACL, and labels for any Synology Drive file or folder.

Instructions

Get detailed metadata (size, owner, ACL, labels) for a specific Drive file or folder.

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_file_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFile or folder path, e.g. '/mydrive/reports/Q1.osheet', or a file ID like '552146100935505098'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4/5.0
Behavior4/5

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

The description indicates a read operation ('get detailed metadata'), and no annotations are provided. It could more explicitly state that the operation is read-only and non-destructive, but the description itself is clear about the action.

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?

The description is a single sentence that efficiently conveys the action, resource, and scope. Every word adds value, with no repetition or filler.

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 tool with one parameter and no output schema, the description adequately states the type of data returned (size, owner, ACL, labels). It does not specify the output format but is sufficient for an agent to understand the tool's purpose.

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?

The input schema has 100% coverage with a well-described 'path' parameter including examples. The description adds no additional semantic information beyond what the schema provides, so a baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states it retrieves detailed metadata for a Drive file or folder, listing specific metadata types (size, owner, ACL, labels). This distinguishes it from sibling tools like 'drive_list_files' (list files) and 'drive_get_sharing_link' (get share link), making the purpose unambiguous.

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?

The description implies use for getting metadata of a specific file, but it does not explicitly state when to use this tool versus alternatives like 'drive_get_sharing_link' or 'drive_list_files'. No 'when not to use' or alternative suggestions are provided.

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

Deploy Server

Other Tools