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

ABAP-ADT-API MCP-Server

by dachienit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

abapDocumentation

Retrieve ABAP documentation for specific code objects to understand functionality and implementation details within ABAP systems.

Instructions

Retrieves ABAP documentation.

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": {
      "objectUri": "<objectUri>",
      "body": "<body>",
      "line": "<line>",
      "column": "<column>"
    },
    "name": "abapDocumentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectUriYes
bodyYes
lineYes
columnYes
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2/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. It only indicates a read operation ('retrieves') but does not disclose parameter expectations, return format, or any behavioral details such as whether login is required or what happens on failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, but it is under-specified, providing no more information than the tool name. It fails to earn its place due to lack of useful content.

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

Completeness1/5

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

For a tool with 5 parameters, no annotations, and no output schema, a one-sentence vague description is completely inadequate. The agent lacks essential information about invocation context, parameter meaning, and expected results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema lists 5 properties with zero documentation, and the description adds absolutely no parameter semantics. The agent cannot infer what 'body', 'line', 'column', 'objectUri', or 'language' mean or how they relate to retrieval.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Retrieves ABAP documentation' uses a clear verb and resource, but it lacks specificity about what documentation, for which objects, or how it differs from sibling tools like findDefinition or objectStructure. It's vague rather than tautological.

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. The description merely states an action with no context, prerequisites, or exclusions, leaving the agent without direction.

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