Skip to main content
Glama

get_collection_item

Retrieve a specific item from a collection by its ID, including related records through populate.

Instructions

Récupère un item spécifique par son ID avec ses relations (populate)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionYesNom de la collection
idYesID de l'item (UUID)
populateNoRelations à inclure, séparées par des virgules

Implementation Reference

  • Handler case for 'get_collection_item' tool: extracts 'collection', 'id', and optional 'populate' from args, then calls skema.getItem() to fetch the item.
    case "get_collection_item": {
      const { collection, id, populate } = args as {
        collection: string;
        id: string;
        populate?: string;
      };
      result = await skema.getItem(collection, id, { populate });
      break;
    }
  • Schema definition for 'get_collection_item' tool: name, description, and inputSchema requiring 'collection' and 'id' (UUID), with optional 'populate' parameter.
    {
      name: "get_collection_item",
      description: "Récupère un item spécifique par son ID avec ses relations (populate)",
      inputSchema: {
        type: "object",
        properties: {
          collection: {
            type: "string",
            description: "Nom de la collection",
          },
          id: {
            type: "string",
            description: "ID de l'item (UUID)",
          },
          populate: {
            type: "string",
            description: "Relations à inclure, séparées par des virgules",
          },
        },
        required: ["collection", "id"],
      },
    },
  • Helper function getItem() that wraps the mcpCall to 'get_collection_item' with collection, id, and optional populate parameters.
    /**
     * Recupere un item par son ID
     */
    export const getItem = (
      collection: string,
      id: string,
      options?: { populate?: string }
    ) =>
      mcpCall("get_collection_item", {
        collection,
        id,
        populate: options?.populate,
      });
  • src/index.ts:29-32 (registration)
    Tool registration via ListToolsRequestSchema handler that returns the tools array (which includes 'get_collection_item').
    // Liste des outils disponibles
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools,
    }));
  • src/index.ts:32-34 (registration)
    Tool execution handler via CallToolRequestSchema that routes 'get_collection_item' to its handler case.
    }));
    
    // Execution des outils
Behavior2/5

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

No annotations provided, so the description must disclose behavior. It mentions populate but does not specify idempotency, error cases (e.g., item not found), or auth requirements. Minimal behavioral context.

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?

Single, clear, front-loaded sentence with no redundancy. Efficiently communicates core purpose.

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?

Adequate for a simple read operation, but no output schema or return format described. Lacks information on error handling or edge cases, which would be helpful for an 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 coverage is 100%, with each parameter described. The description adds 'populate' mention, but the schema already explains it. Baseline 3 is appropriate as description adds no significant new meaning beyond schema.

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 'Récupère un item spécifique par son ID avec ses relations (populate)', specifying the resource (item by collection and ID) and the key feature (populate). This distinguishes it from sibling tools like get_collection_items (list) and search_collection_items.

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 on when to use this tool versus alternatives (e.g., get_collection_items for lists, search_collection_items for filters). Lacks explicit conditions or exclusions.

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