AgentDrive MCP Server

drive_invite

Invite a human to your organization by email; they receive a verification code to join.

Instructions

Invite a human to your organization by email. They will receive a verification code to join.

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": {
      "email": "<email>"
    },
    "name": "drive_invite"
  }
}

Input Schema

Name	Required	Description	Default
`role`	No	Role in the organization (default: member)	member
`email`	Yes	Email address of the human to invite to your organization

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so description carries full burden. It mentions the outcome (verification code sent) but omits authorization requirements, rate limits, or what happens for existing emails. Core behavior is clear but side effects are missing.

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?

Two sentences, no filler, front-loaded with purpose. Every word serves a purpose.

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 simple invite tool, the description covers the key action and expected follow-up. However, it lacks prerequisites (e.g., who can invite) and error cases. Given no output schema, it is fairly complete but could be slightly richer.

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?

Input schema covers both parameters (email, role) with descriptions. The description adds context about the invitation process (email, verification code) beyond schema but does not elaborate on role parameter significance. With 100% schema coverage, baseline is 3.

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 verb 'Invite' and resource 'a human to your organization by email', distinguishing from sibling tools like drive_share which likely share items. The action is specific and 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 explains the tool's purpose but does not provide guidance on when to use it versus alternatives like drive_share or drive_roles. No explicit 'when to use' or 'when not to use' context is given.

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