Skip to main content
Glama

create_collection_item

Add a new item to a specified collection by providing collection name and item data.

Instructions

Crée un nouvel item dans une collection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionYesNom de la collection
dataYesDonnées de l'item à créer

Implementation Reference

  • src/tools.ts:88-105 (registration)
    Tool registration with name 'create_collection_item' and input schema requiring 'collection' (string) and 'data' (object)
    {
      name: "create_collection_item",
      description: "Crée un nouvel item dans une collection",
      inputSchema: {
        type: "object",
        properties: {
          collection: {
            type: "string",
            description: "Nom de la collection",
          },
          data: {
            type: "object",
            description: "Données de l'item à créer",
          },
        },
        required: ["collection", "data"],
      },
    },
  • Handler case that extracts 'collection' and 'data' from args and calls skema.createItem(collection, data)
    case "create_collection_item": {
      const { collection, data } = args as {
        collection: string;
        data: Record<string, unknown>;
      };
      result = await skema.createItem(collection, data);
      break;
    }
  • Helper function createItem that calls mcpCall('create_collection_item', { collection, data }) to send the JSON-RPC request to the Skema API
    export const createItem = (collection: string, data: Record<string, unknown>) =>
      mcpCall("create_collection_item", { collection, data });
Behavior2/5

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

Without annotations, the description carries the full burden but only says 'creates,' offering no details on side effects, permissions, rate limits, or what gets modified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that efficiently conveys the tool's purpose with no wasted words.

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 nested object parameter 'data' with undefined properties and no output schema, the description lacks details about required fields and return values, making it incomplete for effective agent use.

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 coverage is 100% with descriptions for both parameters, so the description adds no extra meaning beyond the schema. The baseline 3 is appropriate.

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?

The description clearly states the verb 'creates' and the resource 'a new item in a collection,' distinguishing it from sibling tools like batch_create_items and update_collection_item.

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?

No guidance is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites. The usage is only implied by the action of creating a single item.

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/skemacms/mcp-server'

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