Skip to main content
Glama
Sign In
mcp-abap-adt

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetEnhancementImpl

Retrieves source code for a specific enhancement implementation using its name and enhancement spot outside batch mode. Use it to inspect ABAP enhancement logic read-only.

Instructions

[read-only] Retrieve source code of a specific enhancement implementation by its name and enhancement spot. Runs outside batch mode.

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": {
      "enhancement_spot": "<enhancement_spot>",
      "enhancement_name": "<enhancement_name>"
    },
    "name": "GetEnhancementImpl"
  }
}

Input Schema

NameRequiredDescriptionDefault
enhancement_nameYes[read-only] Name of the enhancement implementation
enhancement_spotYesName of the enhancement spot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden: it does declare read-only and discloses the non-batch execution constraint, which is genuine behavioral information beyond the schema. It is silent on what happens when the implementation is not found, whether the source is truncated, or any authorization requirements.

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 read-only tag and the core action front-loaded, and the execution-mode caveat tacked on at the end. Efficient, with only slight redundancy between the "[read-only]" tag and the schema's own repeat of that tag.

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

Completeness4/5

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

For a two-parameter, read-only source retrieval tool with no output schema, the description covers what it returns (source code) and the execution context. Only edge-case behavior (missing implementation, large sources) is left unaddressed, which is a minor gap at this complexity.

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 both parameters are already documented in the input schema. The phrase "by its name and enhancement spot" merely restates the parameter names and adds no format, case-sensitivity, or naming-convention detail, so the baseline of 3 applies.

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?

Names a specific verb and resource ("Retrieve source code of a specific enhancement implementation") plus the two identifying keys, so an agent can tell it is a source-read tool rather than a metadata read. It does not differentiate itself from close siblings such as GetEnhancements or GetEnhancementSpot, which an agent would have to disambiguate on its own.

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?

"Runs outside batch mode" is an implicit usage constraint that steers the agent away from BatchBegin/BatchEnd contexts, but there is no explicit when-to-use statement and no named alternative for listing or reading enhancement spots. The guidance is implied rather than stated.

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