Baasix MCP Server

baasix_delete_schema

Delete a collection schema to remove its structure from your Baasix backend, making the collection unavailable for further data operations. Use this tool to clean up unused or obsolete collections.

Instructions

Delete a collection schema

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>"
    },
    "name": "baasix_delete_schema"
  }
}

Input Schema

Name	Required	Description	Default
`collection`	Yes	Collection name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.7Aug 30, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It only says 'Delete', which implies destructive behavior, but it does not mention irreversibility, cascading effects on collections/items, permissions required, or what is returned after deletion.

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 four-word sentence with no filler; every word contributes to the core meaning. Its brevity is appropriate for a one-parameter delete operation.

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?

Although the parameter schema fully covers the input and the operation is simple, the description omits consequences of deletion and the return behavior. No output schema exists and no annotations offset this gap, so an agent lacks important context for a destructive tool.

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?

The single parameter 'collection' is already fully documented in the schema as 'Collection name', so the description adds no additional semantic detail beyond that. With 100% schema coverage, 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 names a precise verb ('Delete') and a specific resource ('collection schema'), which distinguishes it from siblings such as baasix_create_schema, baasix_update_schema, and baasix_get_schema. An agent can immediately identify the schema-deletion operation.

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 description implies the tool is used when a collection schema should be removed, but it does not explicitly state when to use it versus related schema operations, prerequisites, or destructive conditions. Context from the sibling set helps, but no direct guidance is provided.

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

Deploy Server