Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Delete a collection

delete_collection
DestructiveIdempotent

Delete an EMPTY collection's schema. A collection that still has items is refused with its item count — deleting a collection never deletes its items, so delete those first (delete_collection_item) if the user really wants them gone. Built-in collections cannot be deleted.

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site the collection belongs to
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
collection_typeYesThe collection's slug, as list_collections returns it (e.g. "blog", "menu", "products", "faqs").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the bar is lower, yet the description still adds substantive behavior: the refusal response includes an item count, item data survives collection deletion, and built-in collections are immovable. That is exactly the pre-flight context a destructive tool needs.

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?

Three sentences, front-loaded with the core constraint, then failure mode, then the recovery action, then the hard exclusion. No filler and no restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive three-parameter mutation with no output schema, the description covers the safety model (items preserved), the failure path (refusal with item count), the recovery tool, and the built-in exclusion. Nothing material is missing for correct invocation.

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

Parameters5/5

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

Schema coverage is 100% with all three parameters documented, including collection_type's slug format cross-referenced to list_collections. The description adds no per-parameter detail, so 3 would be the baseline for full schema coverage; however, the constraint that the target collection must be empty and non-built-in effectively qualifies which site_id/collection_type values are valid inputs. Boosted slightly above baseline for that input-validity constraint, which no schema field expresses.

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?

States a specific verb and resource plus a hard constraint: 'Delete an EMPTY collection's schema.' The object of deletion (schema, not items) is disambiguated from delete_collection_item and remove_dynamic_collection by naming item deletion as a separate action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-not conditions ('a collection that still has items is refused'), names the prerequisite alternative (delete_collection_item) and the ordering rule ('delete those first'), plus a categorical exclusion ('Built-in collections cannot be deleted'). An agent knows exactly when this call will fail before making it.

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

All Mondovo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources