Skip to main content
Glama

container_create

Create a document container to organize a new knowledge domain or project. Use this to set up isolated document storage; for memory facts, use memory_space_create instead.

Instructions

Create a new container for documents. Use when setting up a new knowledge domain or project. To make a place for memory facts, use memory_space_create instead.

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": "container_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOlder option: "documents" (default) or "memory". Make memory spaces with `memory_space_create` instead
nameYesContainer name (lowercase alphanumeric and hyphens, 2-128 chars)
descriptionNoOptional description for the container

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • addedInput schema / properties / kind
      Added value: +{
      +  "default": null,
      +  "description": "Older option: \"documents\" (default) or \"memory\". Make memory spaces with `memory_space_create` instead",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observedv0.3.2

TDQS

A4.2/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false, so the safety profile is thin and the description carries most of the burden. It adds useful framing (containers hold documents and represent knowledge domains) but says nothing about duplicate-name behavior, permission requirements, or what the caller gets back.

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?

Three short sentences, front-loaded with the action, then use case, then the alternative. Every sentence earns its place with no redundant restatement of the title.

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 three-parameter creation tool with annotations and full schema coverage, the description covers purpose and routing adequately. The remaining gap is the absence of an output schema combined with no mention of what a successful creation returns.

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%, so `name`, `description`, and `kind` are already fully documented in the schema, including the lowercase-hyphen format and the deprecation note on `kind`. The description adds no parameter-level meaning beyond that, which is the expected baseline here.

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?

States a specific verb and resource ("Create a new container for documents") and immediately contrasts it with `memory_space_create` for memory facts, so an agent can distinguish it from the most confusable sibling without opening a schema.

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

Usage Guidelines5/5

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

Provides an explicit usage context ("setting up a new knowledge domain or project") plus a named alternative with the condition that selects it (memory facts → `memory_space_create`). Nothing about when-not-to-use this tool is left to inference.

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