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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetLocalMacros

Reads the local macros include source of an ABAP class in its active or inactive version, returning the class name, version, and source code for review.

Instructions

[read-only] Reads the local macros include of the ABAP class named by class_name, active or inactive version. Returns { class_name, version, part: 'source', source }. Recordable: in batch mode a call is recorded under the next number and answers with empty content; its answer is read by number after the batch ends.

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": {
      "class_name": "<class_name>"
    },
    "name": "GetLocalMacros"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoVersion to read: "active" (default) for the deployed version, "inactive" for the modified version awaiting activation.active
class_nameYesParent class name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv20.1.0
    • changedInput schema / properties / version / description
      Previous value: -"Version to read: \"active\" (default) for deployed version, \"inactive\" for modified but not activated version."New value: +"Version to read: \"active\" (default) for the deployed version, \"inactive\" for the modified version awaiting activation."
  2. Changed1 schema field changedv16.0.0
    • changedInput schema / properties / class_name / description
      Previous value: -"Parent class name (e.g., ZCL_MY_CLASS)."New value: +"Parent class name."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares read-only, discloses the returned field set, and explains the non-obvious batch-mode behavior (empty content, answer retrieved later by number). It omits permission/auth requirements and any error behavior, keeping it just short of 5.

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?

The critical information (what is read, from which class, which version) is front-loaded in the first clause, followed by return shape and batch caveat. Dense but every sentence adds value; the batch sentence is jargon-heavy yet necessary.

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?

There is no output schema, and the description compensates by listing the returned fields, plus it covers the unusual batch-recorded invocation mode. A mutation-free, two-parameter read tool is adequately specified; only error/permission context is missing.

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 coverage is 100%, with the version enum already documented in the schema (active vs inactive). The description restates only that both versions are selectable and adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Reads the local macros include of the ABAP class') plus the version scope, which cleanly separates it from sibling getters like GetLocalTypes and GetLocalDefinitions. An agent can identify the exact artifact returned without opening the schema.

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?

The read-only tag and 'active or inactive version' phrasing imply the read use case, and the batch-mode note tells the agent how calls behave in batch context. However, no alternatives are named and there is no explicit statement of when to prefer this over GetLocalTypes/GetLocalDefinitions or UpdateLocalMacros.

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