Skip to main content
Glama
kajalkhairnarsap

mcp-abap-adt

by kajalkhairnarsap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetClass

Read-onlyIdempotent

Retrieve ABAP class source code by class name. For large classes, page through source using startLine and maxLines to avoid overload.

Instructions

Retrieve ABAP class source code. For large classes, use startLine/maxLines to page through the source instead of retrieving it all at once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxLinesNoMaximum lines to return (1-100000). Omit to request the rest; the byte cap may return fewer lines.
startLineNo1-based line number to start from (default 1). Beyond EOF returns an empty page with hasMore=false.
class_nameYesName of the ABAP class

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.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 and idempotentHint, so the description adds value by explaining paging behavior for large classes. It doesn't contradict annotations and provides useful behavioral context beyond 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences, front-loaded with the main purpose and followed by a targeted usage tip. Every sentence earns its place with no redundancy.

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?

For a read-only retrieval tool with robust annotations and full parameter schema, the description covers the essential usage scenario (paging for large classes). It doesn't specify return format, but the lack of an output schema makes that less critical.

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 parameters are already documented. The description enhances understanding by linking startLine/maxLines to paging for large classes, which adds practical meaning beyond the raw 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?

The description clearly states the action ('Retrieve') and the resource ('ABAP class source code'), distinguishing it from sibling tools that fetch other ABAP artifacts like functions, tables, or programs. The purpose is specific and unambiguous.

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?

The description provides a clear usage hint for large classes, advising to page with startLine/maxLines. It doesn't explicitly contrast with alternatives, but the paging guidance is practical and context-specific.

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