Skip to main content
Glama
Sign In

Azquo

by ai.azquo
OverviewDiscussionsAdmin

Delete database

delete_database
DestructiveIdempotent

Permanently delete an Azquo database by name, with all its names, values and history. NOT REVERSIBLE - there is no restore, and its backups are deleted too. Do not call without the user explicitly asking for this database to be deleted; confirm the name and the business (current_business) with them first. To remove a few names use delete_name (restorable with restore_name); to test changes safely use try_on_copy.

Also removed: reports left linked to no other database or user, its import template if no other database uses it, its upload history, pending uploads and uploaded source files. Reports and templates shared with other databases are kept.

Needs an administrator of the business, or the developer who owns the database; the name must be exact (list_databases). Errors database_not_found for an unknown name. Returns {deleted: true, name} - also when a developer who does not own it is refused silently, so confirm with list_databases afterwards.

Input Schema

NameRequiredDescriptionDefault
nameYesExact name of the database to delete, as shown by list_databases, e.g. Sales_Forecast
businessNoOptional. The business this call is for, by name, e.g. "azquo" - it then runs there whatever business the session is in. Worth giving on writes when you work in more than one business: a new MCP session starts in the login's own business. list_businesses shows the names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / business
      Added value: +{
+  "description": "Optional. The business this call is for, by name, e.g. \"azquo\" - it then runs there whatever business the session is in. Worth giving on writes when you work in more than one business: a new MCP session starts in the login's own business. list_businesses shows the names.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"The database name to delete"New value: +"Exact name of the database to delete, as shown by list_databases, e.g. Sales_Forecast"
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint and non-reversibility, but the description adds cascading deletions (linked reports, import template if unused, upload history, pending uploads, source files) and what is kept, permission requirements (admin or owning developer), and the dangerous silent-refusal behavior that still returns {deleted: true}. This is rich context well beyond the structured data.

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?

Front-loads the irreversible destructive nature, then proceeds in logically grouped blocks: alternatives, cascade effects, permissions, errors, return value. Despite the length, each sentence carries operational weight for a destructive, side-effecting tool.

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?

Given a destructive, cascading operation with no output schema, the description covers permissions, error behavior, the silent-refusal trap, and even the return shape. Nothing an agent needs to call this safely is missing.

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 coverage is 100%, so both parameters are already fully documented in the schema. The description reinforces exact-name matching and the business parameter, but adds little syntax or meaning beyond what the schema and its descriptions already provide — the baseline for high coverage.

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 ('Permanently delete an Azquo database by name') and enumerates the full scope of what is removed. It explicitly differentiates from siblings delete_name and try_on_copy, so an agent can select correctly without opening other schemas.

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/when-not guidance ('Do not call without the user explicitly asking... confirm the name and the business first') and names the alternatives (delete_name for a few names, try_on_copy for safe testing) with the condition that selects them.

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

All Azquo 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