Skip to main content
Glama

DeleteStructure

Delete an ABAP structure from the SAP system with built-in deletion check and optional transport request for local objects.

Instructions

Delete an ABAP structure from the SAP system. Includes deletion check before actual deletion. Transport request optional for $TMP objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
structure_nameYesStructure name (e.g., Z_MY_STRUCTURE).
transport_requestNoTransport request number (e.g., E19K905635). Required for transportable objects. Optional for local objects ($TMP).
Behavior4/5

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

With no annotations, description adds behavioral info: includes a deletion check and optional transport request for $TMP objects. Lacks details on side effects or error behavior, but provides useful context.

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?

Two sentences, concise, front-loaded with main action. Every word adds value.

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?

Covers deletion and transport aspects, but lacks return value or error behavior. Since no output schema, description could describe what the tool returns on success/failure.

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 already describes both parameters (100% coverage). Description adds value by explaining transport_request optionality for $TMP objects, clarifying its practical use.

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?

Clearly states it deletes an ABAP structure, with a specific verb and resource. Distinguishes from sibling Delete tools by specifying the object type and mentioning a deletion check.

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?

Implies usage when deleting ABAP structures, but does not explicitly state when to use vs other Delete tools or when to avoid. No alternative guidance provided.

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/ChinhHN-DEV/abap-mcp-adt'

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