Skip to main content
Glama

create_drive

Idempotent

Create a new Huly Drive space or retrieve an existing one with the same name. Specify members, owners, privacy, and auto-join settings.

Instructions

Idempotently create a Huly Drive space. If an active Drive with the same exact name already exists, returns it with created=false. Initial members and owners accept account UUIDs, exact emails, or exact person names; omitted lists default to the caller.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesa string that will be trimmed
descriptionNoPlain-text Drive description.
privateNoWhether the Drive is private. Defaults to false.
autoJoinNoWhether workspace members should auto-join the Drive. Defaults to false.
membersNoInitial Drive members. Each entry may be an account UUID, exact email address, or exact person name. When omitted, the caller is added.
ownersNoInitial Drive owners. Each entry may be an account UUID, exact email address, or exact person name. When omitted, the caller is the owner.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesThe successful tool result. The same value is also serialized as JSON in the text content for clients that do not read structuredContent.
warningsNoOptional agent-visible warnings about degraded result fidelity. Omitted when the server returned the documented happy-path payload.
Behavior4/5

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

The description adds context beyond annotations by detailing idempotency, member/owner resolution (UUIDs, emails, names), and default behavior when lists are omitted. This enhances understanding of the tool's behavior.

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 only two sentences, efficiently conveying key information without unnecessary words. It is front-loaded with the main action and idempotency.

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?

Given the presence of annotations and an output schema, the description covers essential aspects: creation, idempotency, and member/owner handling. It could mention name trimming or error cases, but schema already handles that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the schema already explains most parameters. The description adds value by clarifying that 'members' and 'owners' accept various identifiers and default to the caller, which compensates for any missing semantic detail.

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 explicitly states 'Idempotently create a Huly Drive space', providing a specific verb and resource. It distinguishes from siblings like 'create_drive_folder' and 'update_drive' by focusing on creation and idempotency.

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

Usage Guidelines4/5

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

The description clearly indicates when to use the tool (to create a drive) and explains the idempotent behavior for duplicates. However, it does not explicitly mention when not to use it or provide alternatives to other tools like 'update_drive'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dearlordylord/huly-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server