Skip to main content
Glama
Sign In
mcp-abap-adt

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetBehaviorDefinitionVersionSource

Retrieves the source code for a RAP behavior definition version specified by content_uri, so you can inspect historical version content.

Instructions

[read-only] Reads the source of the RAP behavior definition version named by content_uri, an entry of the RAP behavior definition's version history. Recordable: in batch mode a call is recorded under the next number and answers with empty content; its answer is read by number after the batch ends.

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": {
      "content_uri": "<content_uri>"
    },
    "name": "GetBehaviorDefinitionVersionSource"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_uriYesOpaque content_uri of a version, from the RAP behavior definition's version history.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv20.1.0
    • changedInput schema / properties / content_uri / description
      Previous value: -"Opaque content_uri taken from a GetBehaviorDefinitionVersions entry."New value: +"Opaque content_uri of a version, from the RAP behavior definition's version history."
  2. Addedv8.5.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and explicitly marks the operation as read-only. It also discloses non-obvious batch behavior: calls are recorded, return empty content in batch mode, and answers are read later by number.

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 front-loaded with the read-only action and resource, then follows with the essential batch-mode caveat. Both sentences carry useful information without redundant restatement.

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 one-parameter read tool, the description covers purpose, read-only status, parameter source, and batch semantics adequately. It stops short of describing normal return content or error behavior, which leaves a minor gap given there is no output schema.

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 single content_uri parameter is already well documented in the schema. The description repeats that it names a version from the RAP behavior definition's version history but adds little beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: reads the source of a RAP behavior definition version identified by content_uri. This implicitly distinguishes it from sibling version-list and version-diff tools, but it does not explicitly name those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It implies the tool is used when a content_uri is available from the RAP behavior definition version history. It also explains batch-mode recording, but it does not explicitly say when to choose this over GetBehaviorDefinitionVersions or GetBehaviorDefinitionVersionDiff.

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