Skip to main content
Glama

Delete definition

delete_definition
Destructive

Delete one business definition from a connection, by its name as get_context lists it (any case). Only when the user asked for it. Changes what every AI tool and person on this connection reads, and is recorded in SaturnSQL with your name. Only make it when the user asked for it or confirmed it. Needs the write scope, the connection's owner or an admin, and a plan that includes Context.

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": {
      "connectionId": "<connectionId>",
      "name": "<name>"
    },
    "name": "delete_definition"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the definition to delete.
connectionIdYesConnection id from list_connections.

Output Schema

NameRequiredDescriptionDefault
deletedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/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 goes further: it discloses the blast radius ('changes what every AI tool and person on this connection reads') and that the action is attributed and recorded in SaturnSQL with the caller's name. That audit-trail and impact information is not derivable from the structured fields.

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 action, then the user-intent gate, then impact and prerequisites — a sensible order. The intent gate is restated twice in slightly different words, which is minor but noticeable redundancy.

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?

An output schema exists, so return values need not be explained. With two parameters, full schema coverage, and permissions, impact, audit logging and intent gating all covered, nothing an agent needs before calling is missing.

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

Parameters4/5

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

Schema coverage is 100% and already explains both parameters, so the baseline would be 3. The description adds real meaning by stating the name is matched case-insensitively ('any case') and should be sourced from get_context, which the schema does not say.

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 ('Delete one business definition from a connection'), scopes it to a single item, and identifies the name source ('as get_context lists it'), which separates it cleanly from upsert_definition.

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 an explicit gating condition ('Only when the user asked for it or confirmed it') rather than a vague hint, and pairs it with the entitlement preconditions (write scope, connection owner or admin, plan including Context) an agent must check before calling.

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.

Resources