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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetLocalDefinitions

Reads the local definitions include of a specified ABAP class in active or inactive version, returning the class name, version, part, and source.

Instructions

[read-only] Reads the local definitions include (the definitions 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": "GetLocalDefinitions"
  }
}

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?

No structured annotations are present, so the description carries the burden and does well: it declares [read-only], states the exact return shape, and — importantly — discloses the batch-mode recording behavior (empty content until read by number). This is genuine behavioral context an agent couldn't infer from the schema.

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?

Read-only tag and core purpose are front-loaded, followed by return shape and batch semantics. The Recordable sentence is long but conveys non-obvious behavior, so it earns its place; slightly dense but not wasteful.

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?

With no output schema, the description supplies the return shape (class_name, version, part, source) and the batch-read caveat, which covers what an agent needs to call and interpret the result. Minor gap: no explicit read-versus-update guidance, but nothing critical 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%, so both class_name and version are already documented in the schema. The description restates that class_name names the class and version is active/inactive, adding little beyond the schema. 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?

Specific verb (Reads) + resource (the local definitions include of the ABAP class) + scoping (active or inactive version). The phrase 'definitions include' cleanly distinguishes it from sibling tools GetLocalTypes and GetLocalMacros without opening any 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 version enum is explained, giving some context for the active/inactive choice, but there is no explicit when-to-use versus siblings (GetLocalTypes, UpdateLocalDefinitions, DeleteLocalDefinitions) or stated prerequisites. Usage is implied by the resource name rather than guided.

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