Skip to main content
Glama
Sign In
ABAP-ADT-API MCP-Server

ABAP-ADT-API MCP-Server

by dachienit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

transportAddUser

Add a user to an ABAP transport request to manage development workflow and access permissions for ABAP system changes.

Instructions

Adds a user to a transport.

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": {
      "transportNumber": "<transportNumber>",
      "user": "<user>"
    },
    "name": "transportAddUser"
  }
}

Input Schema

NameRequiredDescriptionDefault
transportNumberYesThe transport number.
userYesThe user to add.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, but it only states the basic action. It does not disclose side effects, permissions required, behavior when adding an existing user, or return values. This is a significant gap for a mutation tool.

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. It communicates the core action efficiently.

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

Completeness2/5

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

For a simple 2-parameter operation, the description is minimal, but given no annotations, no output schema, and no explanation of return values or error conditions, it is not complete enough. The tool's side effects and context are absent.

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%, so baseline is 3. The description adds no parameter information, and while the schema's descriptions are somewhat tautological ('The user to add.', 'The transport number.'), they are present. No extra semantics are provided.

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?

The description 'Adds a user to a transport.' uses a specific verb and resource, clearly distinguishing it from sibling tools like createTransport and transportSetOwner. It unambiguously states the action and target.

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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description is purely declarative and does not help the agent choose among related transport-management tools.

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