Skip to main content
Glama
AnindyaDR-SAP

mcp-abap-adt

by AnindyaDR-SAP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetBehaviorDefinition

Retrieve RAP Behavior Definition (BDEF) source code from SAP ABAP systems. Page through large definitions using startLine and maxLines to avoid truncation.

Instructions

Retrieve RAP Behavior Definition (BDEF) source code (requires ~NW 7.54 / S/4HANA). For large definitions, 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.
behavior_definition_nameYesName of the RAP Behavior Definition (e.g. I_MY_ENTITY)

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 provided, the description carries the full behavioral burden. It usefully discloses the system requirement (~NW 7.54 / S/4HANA) and the paging behavior, but it does not describe the return format, error behavior, or confirm read-only semantics beyond the word 'Retrieve'.

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 sentences with no filler, front-loads the core purpose, and places the paging guidance exactly where it is actionable. Every word contributes value.

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 retrieval tool with fully documented parameters, the description provides the necessary prerequisite and paging context. It omits an explicit return-format statement, but 'source code' is sufficient given the tool's purpose and name.

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 three parameters at 100% coverage, so the baseline is 3. The description reinforces the paging parameters but does not add meaning beyond the schema, such as format details or edge-case behavior.

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 uses a specific verb ('Retrieve') and a precise resource ('RAP Behavior Definition (BDEF) source code'), making the tool's function unambiguous. The object type is unique among the sibling tools, so an agent can distinguish it without needing to inspect other definitions.

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 gives clear guidance on when to use startLine/maxLines for paging large definitions. It does not explicitly discuss alternatives or exclusions, but the sibling tools are all different object types, so selection is already self-evident.

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