Skip to main content
Glama

cozi_get_lists

Retrieve all shopping and todo lists from Cozi Family Organizer, including item counts and contents for family task management.

Instructions

Get all Cozi lists (shopping and todo lists) with their items. Returns complete list of all lists including item counts and contents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'cozi_get_lists' tool within the executeTool switch statement. It calls client.getLists() and maps the results to include id, title, and item_count for each list.
    case 'cozi_get_lists': {
      const lists = await client.getLists();
      return {
        lists: lists.map(list => ({
          id: list.listId,
          title: list.title,
          item_count: list.items.length,
        })),
      };
    }
  • Input schema definition for the 'cozi_get_lists' tool, specifying no required input parameters as an empty object.
    {
      name: 'cozi_get_lists',
      description: 'Get all Cozi lists (shopping, to-do, etc.)',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:159-168 (registration)
    MCP 'tools/list' handler that registers and exposes the COZI_TOOLS array, including the 'cozi_get_lists' tool schema to the MCP client.
    case 'tools/list': {
      response = {
        jsonrpc: '2.0',
        id: mcpRequest.id,
        result: {
          tools: COZI_TOOLS,
        },
      };
      break;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool retrieves data (implied read-only) and returns 'complete list of all lists including item counts and contents', but lacks details on permissions, rate limits, pagination, error conditions, or whether it returns archived lists. For a read operation with zero annotation coverage, this is insufficient.

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 two concise sentences that efficiently convey the core functionality. It is front-loaded with the main purpose, though it could be slightly more structured by separating scope from return details.

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?

Given zero parameters, no annotations, and no output schema, the description adequately covers the basic purpose but lacks sufficient behavioral context (e.g., response format, error handling). For a read-all tool, it should ideally specify output structure or limitations, but the absence of an output schema increases the burden on the description.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description adds no parameter information, which is appropriate here. Baseline is 4 for zero-parameter tools as no compensation is needed.

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 verb ('Get') and resource ('Cozi lists'), specifying that it retrieves both shopping and todo lists with their items. It distinguishes from 'cozi_get_list' (singular) by indicating it returns 'all lists', but doesn't explicitly contrast with other siblings beyond this scope difference.

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?

The description implies usage when needing all lists with items, but provides no explicit guidance on when to use this versus alternatives like 'cozi_get_list' (singular) or other list/item manipulation tools. No exclusions or prerequisites are mentioned.

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