AgentDrive MCP Server

drive_list

List files in a shared workspace. Filter by path prefix to locate documents in a specific folder.

Instructions

List files in a workspace, optionally filtered by path prefix.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "drive_list"
  }
}

Input Schema

Name	Required	Description	Default
`prefix`	No	Path prefix filter (e.g. "notes/")
`workspace_id`	Yes	Workspace ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates a read-only operation (list), but does not disclose pagination, sorting, permissions, or other behavioral traits. The description is adequate but minimal.

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?

Single sentence, zero wasted words. Appropriate length for a simple list tool.

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

Completeness3/5

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

No output schema, so the agent does not know the return format beyond a list of files. This is a gap, but the description is complete for a basic listing operation. Considering the complexity is low, it is minimally viable.

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% as both parameters have descriptions in the schema. The description adds the phrase 'optionally filtered by path prefix' which reinforces the prefix parameter, but does not add new meaning beyond the schema.

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 the action (List) and resource (files in a workspace), and specifies an optional filter (by path prefix). It distinguishes from siblings like drive_write (write files) and drive_share (sharing) by focusing on listing.

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 usage for listing files, but does not explicitly state when to use this tool versus siblings like drive_search or drive_recall. No exclusion criteria or alternatives are mentioned, which is a gap given the many similar siblings.

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