abap-config-mcp

Get Text Elements

get_text_elements

Read-onlyIdempotent

Retrieve selection texts, text symbols, and list headings for ABAP programs, function groups, or classes; omit the category to fetch all three at once.

Instructions

Read text elements for an ABAP program, function group or class: selection texts (PARAMETERS / SELECT-OPTIONS labels, flagged when they are dictionary references), text symbols (TEXT-001 etc., with their maximum length), and list headings (LISTHEADER, COLUMNHEADER_1..4). Omit category to retrieve all three.

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": {
      "objectType": "<objectType>",
      "objectName": "<objectName>"
    },
    "name": "get_text_elements"
  }
}

Input Schema

Name	Required	Description
`category`	No	selections, symbols or headings. Omit for all three.
`objectName`	Yes	Object name, e.g. ZCAR_MM_ORDERS
`objectType`	Yes	ADT object type, e.g. PROG/P, FUGR/F, CLAS/OC
`connectionId`	No	SAP system connection ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.16.0Nov 12, 2026

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, so the safety profile is covered. The description adds genuine domain behavior beyond that: dictionary-reference flagging for selection texts and maximum length reporting for text symbols, which tell the agent what the payload will contain.

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?

Two sentences, front-loaded with the verb and scope, then the category breakdown and the omit behavior. No filler or redundancy; 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?

There is no output schema, and the description compensates by naming the three result categories and their notable fields (dictionary-reference flag, max length). Required parameters and object type/name examples are covered in the schema, so nothing critical is missing for a correct call.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning to the category enum by mapping each value to concrete ABAP artifacts (PARAMETERS/SELECT-OPTIONS labels, TEXT-001 symbols, LISTHEADER/COLUMNHEADER_1..4). That exceeds what the schema's short enum description conveys.

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 ('Read text elements') and scopes it to three ABAP object kinds (program, function group, class), then enumerates the three artifact classes returned. It is clearly distinguishable from the write-side sibling set_text_elements.

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

Usage Guidelines4/5

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

Gives explicit operational guidance for the retrieve-all case ('Omit category to retrieve all three') and scoping to specific object types. It does not explicitly state when to prefer this over set_text_elements, though the read-vs-write split is strongly implied by naming and annotations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server