Skip to main content
Glama

items-create

items-create

Create case file items of various types including notes, bookmarks, todos, files, invoices, and more with type-specific parameters.

Instructions

Creates a case file item. Set 'type' to choose the item type. Common params: case_id, name/title, parent_id, tags, description. Type-specific: note(content), bookmark(url,title), todo(title,status,priority,due_date), duration(start_time,end_time,billable), expense(description,amount,date), invoice(invoice_number,amount,client_id), file(filename), folder(name), checkbox(label,checked), journal_entry(content,mood), sms(body,to), directory(path), desktop(name).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameNoFilename (file)
notesNoAdditional notes
assigned_toNoWho is responsible (todo)
titleNoTitle (alias for name, used by note/bookmark/todo/journal)
amountNoAmount (invoice, expense)
dateNoDate YYYY-MM-DD (expense)
iconNoIcon identifier (folder)
end_timeNoEnd timestamp ISO8601 (duration)
bodyNoSMS message body (sms)
mime_typeNoMIME type (file)
moodNoMood tag (journal_entry)
invoice_numberNoInvoice number (invoice)
vendorNoVendor name (expense)
start_timeNoStart timestamp ISO8601 (duration)
sizeNoFile size bytes (file)
urlNoURL (bookmark)
tagsNoTags for categorization
checkedNoChecked state (checkbox)
client_idNoClient ID @rid (invoice — creates BillTo edge)
currencyNoCurrency code USD/EUR (invoice, expense)
labelNoLabel text (checkbox)
dataNoAdditional data as JSON (advanced)
case_idYesCase ID (@rid format)
due_dateNoDue date ISO8601 (todo)
nameNoItem name (or use title)
descriptionNoDescription (bookmark, todo, expense, desktop, directory)
formatNoFormat: text, markdown, html (note, journal_entry)
priorityNoPriority: critical, high, medium, low (todo)
toNoRecipient phone E.164 (sms)
statusNoStatus (todo: pending/in_progress/completed, invoice: draft/sent/paid)
contentNoContent text (note, journal_entry)
invoice_dateNoInvoice date YYYY-MM-DD (invoice)
billableNoIs billable? (duration, expense)
parent_idNoParent item ID (for hierarchical nesting)
colorNoDisplay color (folder)
pathNoFilesystem path (directory)
typeYesItem type: note, bookmark, folder, file, todo, checkbox, journal_entry, duration, expense, invoice, sms, desktop, directory
categoryNoCategory. For expenses: software_subscription, one_time_purchase, passthrough, project, service, travel, meals, equipment, hosting, consulting, labor, other. Also used by journal_entry and todo (freeform).
hostNoMachine hostname (directory)
Behavior2/5

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

No annotations provided; description only states it creates an item without discussing side effects, authentication, rate limits, or return behavior. Minimal behavioral context for a write operation.

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?

Single paragraph, front-loaded with primary action, and efficiently lists type-specific parameter groupings. Slightly long due to many types but no wasted sentences.

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?

No output schema; description omits return value (e.g., created item object). Adequate for parameter mapping but lacks completeness on result and validation context.

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 covers all 39 parameters (100% coverage). Description adds value by grouping parameters into common and type-specific sets, clarifying which parameters apply to which item type, exceeding schema descriptions.

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?

Description states 'Creates a case file item' with specific verb and resource, and lists type-specific parameters, effectively distinguishing it from sibling items tools.

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?

Implies usage via parameter grouping but provides no explicit when-to-use, when-not-to-use, or alternatives compared to sibling tools like items-update or items-delete.

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/mstang/casemgr-mcp'

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