Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

CreateStructure

Creates a new ABAP structure in an SAP system in initial state. Add fields or includes afterward using an update call.

Instructions

Create a new ABAP structure in SAP system. Creates the structure object in initial state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detailNoHow much of the answer to return: "terse" (default, the fields you need to act), "full" (the whole parse), "raw" (the document as ADT sent it).terse
fieldsYesDoes not reach creation — the shipped create endpoint posts a metadata document only. Use UpdateStructure (with ddl_code) after creating to set the fields.
activateNoActivate structure after creation. Default: true. Set to false for batch operations (activate multiple objects later).
includesNoDoes not reach creation — see `fields`. Use UpdateStructure (with ddl_code) after creating to set includes.
descriptionNoStructure description. If not provided, structure_name will be used.
package_nameYesPackage name
structure_nameYesStructure name.
master_languageNoOptional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
transport_requestNoTransport request number, not a task. Required for transportable packages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv16.0.0
    • addedInput schema / properties / detail
      Added value: +{
+  "default": "terse",
+  "description": "How much of the answer to return: \"terse\" (default, the fields you need to act), \"full\" (the whole parse), \"raw\" (the document as ADT sent it).",
+  "enum": [
+    "terse",
+    "full",
+    "raw"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / fields / description
      Previous value: -"Array of structure fields"New value: +"Does not reach creation — the shipped create endpoint posts a metadata document only. Use UpdateStructure (with ddl_code) after creating to set the fields."
    • changedInput schema / properties / includes / description
      Previous value: -"Include other structures in this structure"New value: +"Does not reach creation — see `fields`. Use UpdateStructure (with ddl_code) after creating to set includes."
    • changedInput schema / properties / package_name / description
      Previous value: -"Package name (e.g., ZOK_LOCAL, $TMP for local objects)"New value: +"Package name"
    • changedInput schema / properties / structure_name / description
      Previous value: -"Structure name (e.g., ZZ_S_TEST_001). Must follow SAP naming conventions."New value: +"Structure name."
    • changedInput schema / properties / transport_request / description
      Previous value: -"Transport request number (e.g., E19K905635). Required for transportable packages."New value: +"Transport request number, not a task. Required for transportable packages."
  2. Changed1 schema field changedv8.1.0
    • addedInput schema / properties / master_language
      Added value: +{
+  "description": "Optional master/original language for the created object (e.g. \"EN\", \"DE\", \"ZH\"). Defaults to the session language (SAP_LANGUAGE) or EN.",
+  "type": "string"
+}
  3. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only says the object is created in 'initial state.' It omits critical traits such as the two-step create-then-update workflow, activation behavior, transport/lock requirements, and idempotency, all of which matter for a mutating tool.

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?

Two short sentences with the verb and resource front-loaded and no filler. There is mild redundancy between 'Create a new ABAP structure' and 'Creates the structure object,' keeping it just short of a 5.

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?

For a create tool with 9 parameters and no output schema, the description should surface the critical 'metadata-only create, then UpdateStructure with ddl_code' workflow, but it leaves that to the schema. The schema compensates, so the definition is adequate but not self-sufficient.

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% and the schema even explains the non-obvious caveat that `fields` and `includes` do not reach creation. The description itself adds no parameter meaning, so the baseline 3 applies as the schema does all the work.

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 states a specific verb and resource ('Create a new ABAP structure') and adds the scope qualifier that it lands in 'initial state,' which distinguishes it from sibling mutations like CreateTable and from UpdateStructure. It does not explicitly name those siblings, so it falls short of a 5.

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?

The phrase 'initial state' implies a follow-up step is expected, but the description never says when to prefer this over UpdateStructure or CreateTable. The important routing advice (use UpdateStructure with ddl_code after creating) lives in the schema, not the description.

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

Deploy Server

Other Tools