Skip to main content
Glama

Create item

create_item

Create an item in a project. kind is character, place, object, style, sequence or set. The slug (default: derived from name) is unique in the project and is how prompts and tools refer to it, as @slug. parent_item_id makes the item a shot of a sequence item. Pass the item to generate or run_workflow (item) to record outputs as its takes.

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": {
      "project": "<project>",
      "kind": "<kind>",
      "name": "<name>"
    },
    "name": "create_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
nameYes
slugNo
projectYes
descriptionNo
parent_item_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, open-world create operation, so the bar is lower. The description still adds real behavior: slug must be unique within the project and is the handle used as @slug, slug defaults from name, and parent_item_id turns the item into a shot of a sequence item. It does not say what error occurs on a slug collision or what permissions are required.

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?

Four dense sentences, front-loaded with the core action, then kinds, then the slug handle, then hierarchy, then downstream use. No filler; backticked identifiers make parameter references scannable. Slightly information-packed for a single paragraph, but every sentence carries distinct meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the description covers the non-obvious semantics of a 6-parameter creation tool: valid kinds, slug uniqueness and defaulting, and parent-child linkage. Missing failure-mode detail (duplicate slug, unknown project) is minor against what is provided.

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?

Schema description coverage is 0% and there are no enums, so the description must carry the load — and it does for the most ambiguous parameters. It supplies the valid `kind` values (character, place, object, style, sequence, set), the slug default derivation and uniqueness rule, and the hierarchy meaning of parent_item_id. `project`, `name`, and `description` are left to the schema alone.

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?

Opens with a specific verb+resource ('Create an item in a project') and immediately narrows scope by enumerating the six possible kinds. It also clarifies the domain concept of an item (slug handle, parent/child hierarchy) so an agent understands what object it is creating. It does not explicitly contrast with create_project, but the resource distinction is clear enough.

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?

There is useful downstream context — 'Pass the item to generate or run_workflow (item) to record outputs as its takes' — which tells the agent what to do after creation. However, there is no explicit when-to-use rule, no statement of prerequisites (does the project need to exist?), and no exclusions relative to siblings like create_project.

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