Skip to main content
Glama

Create a folder

create_folder

Create a Drive folder to organize diagrams. Requires a YAMLTools API key.

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

Input Schema

NameRequiredDescriptionDefault
nameYesFolder name
parentFolderIdNoParent folder id; omit to create at the Drive root

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It usefully flags the YAMLTools API key requirement, but for a mutation tool it says nothing about behavior on duplicate names, permissions required, reversibility, or what is returned (no output schema exists, so the returned folder id or handle is undocumented).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, both front-loaded and free of padding. It is efficient rather than verbose, though the brevity leans toward under-specification rather than tightness.

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?

For a simple two-parameter creation tool this covers the core action and the auth requirement, but the absence of any output schema means the description should say what the call returns (e.g., the new folder id) and it does not. Error/duplicate behavior is also unaddressed.

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% and both parameters are documented in-schema with meaning (name limits, parentFolderId root fallback). The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('Create a Drive folder') plus a stated purpose ('to organize diagrams'). It is clearly distinguishable from the sibling list_folders and the diagram tools, though it does not explicitly name a sibling to differentiate against.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative mentioned. The phrase 'to organize diagrams' only weakly implies the context (grouping diagram files), leaving the agent to infer any prerequisites or exclusions on its own.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources