mcp-rap-migrator

validate_and_activate

Run syntax check on ABAP objects and activate them via ADT REST. Returns errors for the agent to fix before activation.

Instructions

STEP 4 — Activates one or more ABAP objects via ADT REST. Runs syntax check first, returns errors for agent to fix before activation. Call human_checkpoint with results.

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": {
      "objects": "<objects>"
    },
    "name": "validate_and_activate"
  }
}

Input Schema

Name	Required	Description	Default
`objects`	Yes	List of {type, name} to activate in order

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. States it runs syntax check first and returns errors for the agent to fix before activation, but does not clarify the exact outcome on success (e.g., what is returned after activation), whether activation is atomic, or if partial activation occurs. Missing output schema increases need for transparency.

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?

Extremely concise: two sentences that front-load the step number, purpose, and key behavioral info. Every sentence adds value with no wasted words.

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?

No output schema and description does not explain return values for success, only mentions error returns. Does not specify whether activation is atomic or partial, nor how this integrates with sibling tools like check_released_cds. Lacks sufficient detail for an activation tool in a workflow.

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?

Only one parameter ('objects') with 100% schema coverage, so baseline is 3. Tool description adds no extra meaning beyond the schema's 'List of {type, name} to activate in order' – does not specify valid types or provide additional usage hints.

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 activates ABAP objects via ADT REST, is STEP 4 of a workflow, runs syntax check first, and returns errors. Distinguishes it from siblings like analyze_module_pool (analysis), check_released_cds (checking), create_transport (transport creation), generate_rap_skeleton (code generation), human_checkpoint (checkpoint), and write_abap_object (writing).

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?

Explicitly indicates it's STEP 4, implying sequence, and instructs to call human_checkpoint with results. Provides clear context for use but does not explicitly mention when not to use or alternatives, though step numbering implies prerequisite steps.

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

Deploy Server