Skip to main content
Glama

create_collection

Create a collection (folder) for items, optionally with a budget. Example: name="PC build", budget=1500, budget_currency="NZD".

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_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoMaterial Symbols icon name, default inventory_2
nameYesName, e.g. "Gift Ideas"
colorNoHex color, default #3B82F6
budgetNoSpending target
reasonNoWhy, for the change history
descriptionNoWhat it is for
budget_currencyNoBudget currency, default NZD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / budget / description
      Previous value: -"Total spending target for this collection (e.g. 1500 for \"Build PC under $1500\")"New value: +"Spending target"
    • changedInput schema / properties / budget_currency / description
      Previous value: -"Currency for the budget (default: NZD)"New value: +"Budget currency, default NZD"
    • changedInput schema / properties / color / description
      Previous value: -"Hex color for the collection (e.g. \"#3B82F6\", \"#22C55E\", \"#A855F7\", \"#EC4899\", \"#F59E0B\", \"#EF4444\"). Default: #3B82F6"New value: +"Hex color, default #3B82F6"
    • changedInput schema / properties / description / description
      Previous value: -"Short description of what this collection is for"New value: +"What it is for"
    • changedInput schema / properties / icon / description
      Previous value: -"Material Symbols icon name (e.g. \"devices\", \"home\", \"shopping_bag\", \"checkroom\", \"directions_car\", \"favorite\"). Default: inventory_2"New value: +"Material Symbols icon name, default inventory_2"
    • changedInput schema / properties / name / description
      Previous value: -"Collection name, e.g. \"Gaming Setup\" or \"Gift Ideas\""New value: +"Name, e.g. \"Gift Ideas\""
    • changedInput schema / properties / reason / description
      Previous value: -"Why this change was made (shown to user in change history)"New value: +"Why, for the change history"
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds essentially nothing beyond that: the optional budget mention is already in the schema, and there is no disclosure of duplicate-name behavior, permission requirements, or what the new collection's identifier/response looks like.

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?

A single front-loaded sentence stating the action and optional budget, followed by a compact example. Efficient, though the example largely restates values already present in the schema's own examples and defaults.

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 7-parameter creation tool with full schema coverage and no output schema, the description covers what the tool makes and its one clearly optional dimension (budget). Missing only edge-case behavior (duplicate names, validation failures) that an agent might want before calling.

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% (icon defaults, color defaults, name length bounds, budget meaning are all documented), so baseline 3 applies. The example showing name, budget, and budget_currency together weakly illustrates that budget pairs with a currency, but adds no constraints or defaults beyond the schema.

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 collection (folder) for items") and clarifies that the collection is a folder holding items, which distinguishes it from item-level siblings like add_item and update_item. It does not explicitly contrast with update_collection or delete_collection, but the creation intent is unambiguous.

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 when-to-use or when-not-to-use guidance, and no mention of prerequisites such as whether collection names must be unique or what happens if a collection already exists. The example implies a typical call but does not route the agent between this tool and update_collection.

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