Skip to main content
Glama

Sap Se24 Lookup

sap_se24_lookup
Read-only

Retrieve structured class or interface metadata from SAP SE24, including methods, parameters, attributes, and implemented interfaces for one or multiple classes.

Instructions

Look up class/interface metadata from SE24 (Class Builder). If sap-adt is available, prefer its get_source/get_class_definition tools. USE THIS instead of sap_transaction('SE24') - faster and returns structured data. Returns class structure including methods with parameters, attributes, and implemented interfaces. Supports single class or list of classes. Each method includes: name, visibility, parameters, exceptions, and description.

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": {
      "classes": "<classes>"
    },
    "name": "sap_se24_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
classesYesSingle class/interface name or list of names (e.g., 'CL_SALV_TABLE' or ['CL_SALV_TABLE', 'CL_ABAP_CHAR_UTILITIES'])
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.
output_fileNoIf provided, write full results to this JSON file and return summary. Recommended for >5 classes to avoid context overflow.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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=true and openWorldHint=false, and the description adds genuine context beyond them: structured output versus screen scraping, relative speed, and batch support for class lists. It does not cover auth/prerequisite details or how the summary-vs-file return mode behaves at the top level (that lives only in the schema), so it stops short of full transparency.

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?

Front-loaded with the purpose and the sibling routing advice before the return-value detail, and every sentence is short and scannable. Minor redundancy between 'methods with parameters, attributes, and implemented interfaces' and the later per-method field list slightly inflates the length.

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 a read-only lookup with a full schema and an output schema, the description supplies everything an agent still needs: what the tool reads, why to prefer it over the transaction route, and what the returned structure contains. The extra return-field detail is redundant with the output schema but not harmful.

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 description coverage is 100%, so all four parameters are already documented, including the string-or-array form of 'classes' and the output_file overflow advice. The description only restates that single-or-list input is supported, adding no syntax or format detail 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?

States a specific verb and resource ('Look up class/interface metadata from SE24 (Class Builder)') and immediately distinguishes itself from the sibling sap_transaction('SE24') route. An agent can tell what it gets back 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 Guidelines5/5

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

Explicitly names the preferred alternative when sap-adt is present (get_source/get_class_definition) and explicitly says to use this instead of sap_transaction('SE24'), with the reason (faster, structured data). Both the when-to-use and when-to-use-something-else conditions are stated.

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