Skip to main content
Glama
AnindyaDR-SAP

mcp-abap-adt

by AnindyaDR-SAP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetInterface

Retrieve ABAP interface source code from SAP systems. For large interfaces, specify a start line and maximum lines to page through the source instead of loading it all at once.

Instructions

Retrieve ABAP interface source code. For large interfaces, 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.
interface_nameYesName of the ABAP interface

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that large interfaces should be paged, which hints at size-related behavior, but it doesn't state read-only intent, error cases like nonexistent interfaces, or how the source is returned. This is adequate but not rich.

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 core purpose and immediately followed by the key usage tip. No filler or 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 simple source-retrieval tool with three well-documented parameters, the description conveys purpose and the main operational concern. Without an output schema it could mention the return format explicitly, but the wording 'source code' makes it sufficiently clear.

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 the baseline is 3. The description adds the context that startLine/maxLines are for paging large interfaces, reinforcing the schema, but doesn't add meaning beyond it.

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?

Description uses a specific verb and resource: 'Retrieve ABAP interface source code.' This clearly distinguishes it from sibling getters targeting different object types (class, program, table, etc.) without ambiguity.

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?

It explicitly advises using startLine/maxLines for large interfaces, giving practical pagination guidance. It does not explicitly list when not to use the tool, but the object-type scope and sibling names make the intended use clear.

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