Skip to main content
Glama
Sign In
Skema MCP Server

Skema MCP Server

by skemacms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_collection_item

Delete a specific item from a collection by providing its ID and the collection name.

Instructions

Supprime un item d'une collection

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collection": "<collection>",
      "id": "<id>"
    },
    "name": "delete_collection_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
collectionYesNom de la collection
idYesID de l'item à supprimer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.3

TDQS

B3.2/5.0
Behavior2/5

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

Without annotations, the description only states it 'deletes' but does not disclose additional behavioral traits such as irreversibility, permissions needed, side effects, or error handling.

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?

Exceptionally concise single sentence that front-loads the action without any extraneous 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?

For a destructive operation with no output schema, the description lacks important details like return value, confirmation, error cases, and permanence.

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?

Input schema has 100% coverage with descriptions for both parameters. The description adds no extra meaning beyond the schema, so a baseline of 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 action: deleting an item from a collection. It uses a specific verb and resource, distinguishing it from sibling tools like create, update, batch, etc.

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., batch delete, update). The description implies deletion but does not specify prerequisites or context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools