Skip to main content
Glama

sap-system-delete

DestructiveIdempotent

Remove an existing SAP system from the Simplifier Low Code Platform by specifying its name to manage system configurations.

Instructions

Delete an existing SAP system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Implementation Reference

  • The handler function for the 'sap-system-delete' tool. It wraps the deletion call to simplifier.deleteSapSystem with tracking and error handling using wrapToolResult.
    async ({ name }) => {
      return wrapToolResult(`Delete SAP system ${name}`, async () => {
        const trackingKey = trackingToolPrefix + toolNameSapSystemDelete;
        return await simplifier.deleteSapSystem(name, trackingKey);
      })
    });
  • Zod input schema for the tool, defining a single required 'name' parameter of type string.
    {
      name: z.string()
    },
  • Direct registration of the 'sap-system-delete' tool using server.tool(), including name constant, description, input schema, metadata hints, and handler function.
    const toolNameSapSystemDelete = "sap-system-delete";
    server.tool(toolNameSapSystemDelete, `# Delete an existing SAP system`,
      {
        name: z.string()
      },
      {
        title: "Delete a SAP system",
        readOnlyHint: false,
        destructiveHint: true,
        idempotentHint: true,
        openWorldHint: false
      },
      async ({ name }) => {
        return wrapToolResult(`Delete SAP system ${name}`, async () => {
          const trackingKey = trackingToolPrefix + toolNameSapSystemDelete;
          return await simplifier.deleteSapSystem(name, trackingKey);
        })
      });
  • Top-level registration call to registerSapSystemTools within the main registerTools function, which registers all tools including sap-system-delete.
    registerSapSystemTools(server, simplifier)
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, which the description doesn't contradict. The description adds minimal context by specifying 'existing SAP system,' implying it won't work for non-existent systems, but doesn't elaborate on permissions, confirmation requirements, or recovery options beyond what annotations provide.

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, front-loaded sentence with zero waste. Every word contributes directly to stating the tool's purpose without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's destructive nature (per annotations) and lack of output schema, the description is minimally adequate but incomplete. It doesn't address potential side effects, error conditions, or what happens post-deletion, which would be valuable for a destructive operation.

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 0%, with one parameter 'name' undocumented in the schema. The description doesn't add any parameter details beyond what's implied by the tool name, failing to compensate for the coverage gap. Baseline 3 applies as the schema provides structure but no descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Delete') and target resource ('an existing SAP system'), providing specific verb+resource pairing. However, it doesn't explicitly differentiate from sibling tools like 'sap-system-update' or other delete operations, which would be needed for a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'sap-system-update' and multiple other delete operations, there's no indication of prerequisites, appropriate contexts, or when-not-to-use scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/simplifier-ag/simplifier-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server