Skip to main content
Glama

Read Text Elements

sap_get_text_elements
Read-onlyIdempotent

Read ABAP text elements (text symbols, selection texts, list headings) for programs, classes, or function groups to identify blank selection screens and missing labels.

Instructions

Read a program's / class's / function group's text elements: text symbols (TEXT-nnn), selection texts (parameter/select-option labels), and list headings.

Args:

  • object_type: 'program' | 'class' | 'function_group'.

  • object_name (string).

  • kind (string): one of 'symbols', 'selections', 'headings'; omit for all three.

  • response_format.

Returns (json): { objectType, objectName, kinds: [{ kind, entries: [{id, text, maxLength?, ddicReference?}], raw, note? }] }. Symbol ids are the 3-character numbers behind TEXT-nnn; selection ids are parameter / select-option names; heading ids are listHeader and columnHeader_1..4.

Examples:

  • "Why is my selection screen blank?" -> object_type='program', object_name='ZFI_POST', kind='selections'.

  • "What are ZCL_FOO's text symbols?" -> object_type='class', object_name='ZCL_FOO', kind='symbols'. Notes:

  • A kind the object does not use returns an empty list, not an error (a class typically has symbols only).

  • Texts come from the object's ORIGINAL (master) language pool, which is not necessarily English — SAP standard objects often return German.

  • ddicReference marks a selection text inherited from the DDIC data element rather than maintained locally.

  • Write them back with sap_set_text_elements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoRead only one kind ('symbols' | 'selections' | 'headings'). Omit for all three.
object_nameYesObject name (e.g. 'ZFI_POST', 'ZCL_FOO').
object_typeYes'program', 'class', or 'function_group' (pass the function GROUP name, not a module).
response_formatNoOutput format: 'markdown' (human-readable, default) or 'json' (structured).markdown
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond that: texts come from the original master language pool (often German), unused kinds return empty lists, ddicReference indicates inherited selection texts, and the exact JSON return shape is documented.

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?

The description is structured with Args, Returns, Examples, and Notes sections, each earning its place. It is longer than minimal, but every section conveys non-obvious information needed for correct use, and the core purpose is front-loaded.

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

Completeness5/5

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

Given there is no output schema, the description fully compensates by documenting the return shape, ID semantics, edge cases, language-pool behavior, and examples. An agent has enough information to call the tool correctly and interpret the result accurately.

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?

The input schema already documents all four parameters with 100% coverage, including enums, defaults, and illustrative object names. The description's Args section mostly restates the schema; the examples and notes add usage context but little new parameter-level meaning.

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?

The description states a specific verb ('Read') and resource ('program's / class's / function group's text elements'), and enumerates the exact kinds of text elements returned. It is immediately distinguishable from sibling tools like sap_get_source and sap_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 Guidelines5/5

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

The description gives concrete examples mapping user questions to the right object_type and kind values, notes that unused kinds return empty lists rather than errors, and explicitly refers to sap_set_text_elements for writing texts back. This gives an agent clear routing guidance without relying on inference.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/appmaster3000/sap-abap-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server