Skip to main content
Glama

cozi_add_item

Add new items to your Cozi family organizer lists. Specify the list ID and item description to create shopping lists or todo items that sync across family members.

Instructions

Add a new item to a Cozi list. The item will be added to the specified list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYesThe ID of the list to add the item to
textYesThe text/description of the item

Implementation Reference

  • Handler for the cozi_add_item tool. Calls CoziClient.addItem with list_id and text, returns success message.
    case 'cozi_add_item': {
      await client.addItem(args.list_id, args.text);
      return {
        success: true,
        message: `Added "${args.text}" to list`,
      };
    }
  • src/tools.ts:41-58 (registration)
    Registers the cozi_add_item tool in the COZI_TOOLS array, including name, description, and input schema.
    {
      name: 'cozi_add_item',
      description: 'Add a new item to a Cozi list',
      inputSchema: {
        type: 'object',
        properties: {
          list_id: {
            type: 'string',
            description: 'The ID of the list to add the item to',
          },
          text: {
            type: 'string',
            description: 'The text/name of the item to add',
          },
        },
        required: ['list_id', 'text'],
      },
    },
  • Defines the input schema for cozi_add_item tool: requires list_id and text strings.
    inputSchema: {
      type: 'object',
      properties: {
        list_id: {
          type: 'string',
          description: 'The ID of the list to add the item to',
        },
        text: {
          type: 'string',
          description: 'The text/name of the item to add',
        },
      },
      required: ['list_id', 'text'],
    },
  • Core implementation of adding an item via POST request to Cozi API endpoint.
    async addItem(listId: string, text: string): Promise<void> {
      await this.request(`/${this.accountId}/list/${listId}/item/`, {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },
        body: JSON.stringify({ text }),
      });
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the item 'will be added to the specified list,' which implies a write operation but doesn't cover permissions, error handling, or response format. For a mutation tool without annotations, this leaves significant gaps in understanding how it behaves beyond the basic action.

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?

The description is a single, efficient sentence that front-loads the core action ('Add a new item to a Cozi list') and adds a clarifying detail. There's no wasted verbiage, and it's appropriately sized for a simple tool. However, it could be slightly more structured by explicitly separating purpose from constraints.

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

Completeness2/5

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

Given the tool's complexity (a mutation with no annotations and no output schema), the description is incomplete. It lacks details on behavioral traits like authentication needs, error cases, or what the response contains. For a tool that modifies data, this minimal description doesn't provide enough context for safe and effective use by an AI agent.

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%, with both parameters (listId and text) clearly documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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?

The description clearly states the action ('Add a new item') and resource ('to a Cozi list'), making the purpose unambiguous. It distinguishes this from sibling tools like cozi_create_list or cozi_edit_item by focusing on item addition rather than list creation or item modification. However, it doesn't explicitly differentiate from cozi_mark_item_complete/incomplete, which are also item-related but for status changes.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing list), exclusions, or comparisons to siblings like cozi_edit_item for modifying items or cozi_remove_item for deletion. Usage is implied through the action but lacks explicit context for selection.

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/BrandCast-Signage/cozi-mcp-server'

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