Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ActivateInterface

Activates an ABAP interface that remains inactive after creation or update, resolving the inactive status so it can be used in SAP.

Instructions

Activate an ABAP interface. Use after CreateInterface or UpdateInterface if the object remains inactive.

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
session_idNoSession ID from GetSession. If not provided, a new session will be created.
session_stateNoSession state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.
interface_nameYesInterface name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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 / interface_name / description
      Previous value: -"Interface name (e.g., ZIF_MY_INTERFACE)."New value: +"Interface name."
  2. Addedv6.5.1

TDQS

A3.5/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 burden of behavioral disclosure for a mutation tool. It hints at a state transition (inactive -> active) but says nothing about idempotency, required locks/transport entry, permissions, whether activation can partially succeed, or what an already-active object returns. That is a substantial gap for an activation operation.

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, zero waste, with the purpose and the trigger condition both front-loaded. Nothing is repeated from the schema or title.

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?

With no output schema and no annotations, the description should compensate more than it does. It covers purpose and trigger adequately for a single required parameter, but omits the failure/return behavior an agent needs to interpret an activation result.

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%, including a documented enum for 'detail' and an explanation of session_id/session_state, so the schema already carries parameter meaning. The description adds nothing about parameters, which is acceptable at this coverage level but not above baseline.

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?

States a specific verb and resource ('Activate an ABAP interface'), which is unambiguous and matches the naming family of ActivateClass/ActivateTable/etc. It does not, however, distinguish itself from the generic sibling ActivateObjects, which could plausibly activate an interface too, so the agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear trigger condition: 'Use after CreateInterface or UpdateInterface if the object remains inactive.' That tells the agent when the tool is warranted rather than leaving it to inference. It stops short of naming alternatives (e.g., ActivateObjects) or explaining what to do if activation fails.

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