Skip to main content
Glama
Sign In
@callirra/mcp

@callirra/mcp

Official
by callirra-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_collection

DestructiveIdempotent

Deletes an owned collection by ID and removes its membership grouping, so agents can clean up unused collection records.

Instructions

Delete an owned collection and remove its membership grouping.

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": {
      "id": "<id>"
    },
    "name": "delete_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations by disclosing that the collection's membership grouping is also removed and by scoping the operation to owned collections.

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 front-loaded sentence with no wasted words, and the key action and consequence are stated immediately.

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 rich destructive/idempotent annotations and no output schema, the description covers the core effect and an important side effect. However, for a destructive mutation it does not explain what happens to assets contained in the collection, whether ownership is enforced, or how the collection identifier is supplied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required 'id' parameter, so the schema does not explain what the value represents or its constraints. The description does not mention the identifier at all and only indirectly implies that it identifies a collection, leaving a gap the schema cannot fill.

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 states a specific verb and resource ('Delete an owned collection') plus an additional consequence ('remove its membership grouping'), which clearly distinguishes it from collection read/create/update siblings. It stops short of explicitly differentiating from other delete tools such as delete_asset.

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 word 'owned' implies a precondition, and deletion of a collection is intrinsically clear, but the description does not say when to use this versus updating or listing collections, nor does it mention exclusions or alternatives. Usage is therefore implied rather than guided.

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