AgentDrive MCP Server

drive_roles

Control access to shared workspaces by assigning, listing, or removing view, comment, or edit roles for specific email addresses.

Instructions

Manage per-workspace role delegation. Assign, list, or remove access for specific emails (view/comment/edit).

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>",
      "action": "<action>"
    },
    "name": "drive_roles"
  }
}

Input Schema

Name	Required	Description
`email`	No	Email address (required for assign/remove)
`action`	Yes	Action: assign a role, list all roles, or remove a role
`permission`	No	Permission level (required for assign)
`workspace_id`	Yes	Workspace ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description bears full burden. It states the actions but does not disclose side effects (e.g., role overriding, error handling) or authentication requirements. This is minimal behavioral disclosure.

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 clearly front-loads the purpose and enumerates actions and permissions. No wasted words.

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?

Given 4 parameters, no output schema, and no annotations, the description covers the primary actions and permissions but lacks details on behavior for duplicate assignments, removal of non-existent roles, or return format. Adequate but with gaps.

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 has 100% coverage with descriptions. The description adds context that this is about delegation but does not provide additional parameter meaning beyond schema. Baseline 3 applies.

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?

Description clearly states it manages per-workspace role delegation, specifying three actions (assign, list, remove) and permission levels (view, comment, edit). This distinguishes it from sibling tools like drive_share or drive_invite.

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 role management but does not provide explicit guidance on when to use this tool over alternatives like drive_share or drive_invite. No exclusions or context are given.

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