Skip to main content
Glama
Sign In

Azquo

by ai.azquo
OverviewDiscussionsAdmin

Delete import template

delete_import_template
DestructiveIdempotent

Permanently delete one import template (the workbook of rules that interprets incoming data files) and its file on disk. NOT REVERSIBLE - there is no restore; read it first with read_workbook if its rules may be wanted again. Do not delete without the user asking for it.

Get the id from list_import_templates. Administrators only, and only templates in the current business. A database that used the template is not updated and still points at the deleted id, so imports into it lose those rules; list_database_sheets shows which template each database uses.

Returns {deleted: true, id}. That is returned even when nothing was removed (unknown id, other business, or not an administrator), so call list_import_templates afterwards to confirm it has gone.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric import template id, as returned by list_import_templates, e.g. 42
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 / id / description
      Previous value: -"Import template ID"New value: +"Numeric import template id, as returned by list_import_templates, e.g. 42"
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds substantial context beyond them: irreversibility with no restore, deletion of the on-disk file, the authorization scope, the downstream effect that referencing databases keep pointing at a dead id and lose those rules, and the critical quirk that {deleted: true, id} is returned even when nothing was removed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the destructive warning, then prerequisites, side effects, and return caveat in a logical order. Every sentence carries information, though the return-value caveat and the database-pointer consequence make it longer than a typical tool description.

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 mutation with no output schema, the description supplies the missing return-value semantics ({deleted: true, id}) including the false-success caveat, plus auth scope and side effects. Nothing an agent needs to call this safely is absent.

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%, so both id and business are already documented in the schema. The description only restates that the id comes from list_import_templates and does not add format or edge-case detail beyond what the schema provides, so the baseline of 3 applies.

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 (delete) and resource (import template), and defines what the resource actually is: 'the workbook of rules that interprets incoming data files'. This distinguishes it cleanly from siblings like delete_database, delete_report and delete_name.

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?

Explicit when/when-not guidance: read first with read_workbook if the rules may be wanted, and 'Do not delete without the user asking for it.' It also names list_import_templates for obtaining the id and constrains usage to administrators in the current business.

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