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

abap-config-mcp

by netweaver1970
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get ABAP Object Info

get_abap_object_info
Read-onlyIdempotent

Reads ABAP object metadata (name, type, description, owner, language, version, URL, includes) from an ADT URL to identify objects before fetching source or transport details; read-only.

Instructions

Read an ABAP object's metadata from its ADT URL: name, type, description, responsible user, language, version and URL, plus its includes for objects that have them (e.g. classes). Does not return source code; use get_abap_object_lines for that and get_transport_for_object for transport and lock state. Read-only. Find the URL with search_abap_objects.

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": {
      "url": "<url>"
    },
    "name": "get_abap_object_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesADT object URL, without /source/main (e.g. /sap/bc/adt/programs/programs/ZREPORT, /sap/bc/adt/oo/classes/zcl_order_api)
connectionIdNoSAP system connection ID (default connection if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.16.2
    • changedInput schema / properties / connectionId / description
      Previous value: -"SAP system connection ID"New value: +"SAP system connection ID (default connection if omitted)"
    • changedInput schema / properties / url / description
      Previous value: -"ADT URL of the object (e.g. /sap/bc/adt/programs/programs/Z_MY_PROG)"New value: +"ADT object URL, without /source/main (e.g. /sap/bc/adt/programs/programs/ZREPORT, /sap/bc/adt/oo/classes/zcl_order_api)"
  2. First observedv1.16.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, and the description reinforces this with 'Read-only' without contradicting anything. It adds real value by disclosing the returned metadata fields and the includes behavior for objects like classes, which matters because no output schema exists. It does not discuss error cases (e.g. invalid URL/system) or connection fallback behavior beyond what the schema states.

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?

Three tight sentences: capability and return shape first, exclusions and alternatives second, access mode and URL acquisition last. No filler, no repetition of the title, and every clause carries information.

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 carries the return-shape burden and does so by listing the metadata fields and the includes variant. Combined with full schema coverage and read-only annotations, an agent has enough to call this correctly. Only minor gaps remain, such as what happens when the object is locked or the URL is malformed.

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 both url and connectionId already documented including the '/source/main' exclusion and default-connection note. The description only reinforces that the URL is an ADT URL and points to search_abap_objects as its source, so it adds marginal but non-zero meaning beyond the schema.

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?

Opens with a specific verb and resource ('Read an ABAP object's metadata from its ADT URL') and enumerates exactly what comes back: name, type, description, responsible user, language, version, URL, and includes. It also states the negative scope ('Does not return source code'), which cleanly separates it from get_abap_object_lines and get_transport_for_object.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use get_abap_object_lines for source, get_transport_for_object for transport and lock state, and search_abap_objects to obtain the required URL. That covers both when to use this tool and when to pick an alternative, plus the prerequisite for the required parameter.

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