delete_collection
Delete a document collection and all of its records.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Collection name to delete. |
demo.st
by st.demo
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- Added
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of disclosing behavior. It discloses the cascading deletion of all records, which is important, but it does not mention irreversibility, required permissions, or any side effects beyond the records themselves.
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 is front-loaded with the action and resource. Every word earns its place, with no filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with one parameter and no output schema. The description covers the target and the destructive scope, which is sufficient for basic invocation, though an explicit 'permanent' or 'irreversible' warning would make it more complete.
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 description coverage is 100%, and the parameter description ('Collection name to delete') fully explains the name parameter. The tool description adds no extra semantic value beyond the schema, so the 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 verb ('Delete'), the resource ('document collection'), and the scope ('all of its records'), which distinguishes it from siblings like delete_record. It is specific and unambiguous.
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 given on when to use this tool versus alternatives. It does not mention that delete_record should be used for individual records or indicate any preconditions or situations to avoid.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4/5.0
Disambiguation5/5
Each tool targets a distinct resource and action: subdomain availability, site content, collections, records, and API keys. There is no meaningful overlap between tools like upload_site and create_collection, or delete_record and upsert_record. Even similar operations (reserve vs. release, create vs. delete) are clearly scoped.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using lowercase with underscores, such as check_subdomain_availability, clear_site, and rotate_site_api_key. Verb forms are uniform and predictable, making it easy to guess related operations. No mixed conventions or vague names.
Tool Count5/5
With 13 tools, the surface is well-scoped for a demo platform covering subdomain management, site deployment, document storage, and API key handling. Each tool has a clear purpose, and the count is within the ideal 3-15 range. No redundancy or bloat.
Completeness4/5
The tool set covers nearly all essential workflows: subdomain lifecycle (reserve, check, release), site deployment (upload, clear), collection/record CRUD (create, delete, list, upsert), and API key management (get, rotate). Minor gaps exist, such as no update_collection or get_site details, but these are not critical for core usage. Overall, the surface is functionally complete for the stated purpose.