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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetBehaviorDefinitionVersionDiff

Compare two RAP behavior definition versions from version history and return a unified diff of their sources. Use it to review what changed between an old and a new version.

Instructions

[read-only] Compares the two RAP behavior definition versions named by content_uri_from and content_uri_to, entries of its version history: answers the unified diff of their sources. 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_from": "<content_uri_from>",
      "content_uri_to": "<content_uri_to>"
    },
    "name": "GetBehaviorDefinitionVersionDiff"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_uri_toYesOpaque content_uri of the NEW/compare version, from the RAP behavior definition's version history.
content_uri_fromYesOpaque content_uri of the OLD/base version, from the RAP behavior definition's version history.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv20.1.0
    • changedInput schema / properties / content_uri_from / description
      Previous value: -"Opaque content_uri of the OLD/base version (from a GetBehaviorDefinitionVersions entry)."New value: +"Opaque content_uri of the OLD/base version, from the RAP behavior definition's version history."
    • changedInput schema / properties / content_uri_to / description
      Previous value: -"Opaque content_uri of the NEW/compare version (from a GetBehaviorDefinitionVersions entry)."New value: +"Opaque content_uri of the NEW/compare version, from the RAP behavior definition's version history."
  2. Addedv8.5.0

TDQS

A3.9/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 burden and discloses non-obvious behavior: it is read-only, and in batch mode the call is recorded under the next number and returns empty content whose answer is fetched later by number. It omits error/failure semantics (e.g. invalid or non-adjacent version URIs) and any size limits on the diff, which keeps it from a 5.

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?

Two sentences, purpose front-loaded first, with the read-only marker and the batch caveat trailing. The batch sentence is dense and slightly convoluted ('Recordable: ... recorded under the next number'), but every clause carries information.

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 two-parameter read tool with no annotations and no output schema, the description covers what it does, what it returns (a unified diff), and how it behaves inside a batch. What remains unstated is failure/edge-case handling, which is minor for this tool shape.

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 coverage is 100% and the schema already labels content_uri_from as OLD/base and content_uri_to as NEW/compare. The description restates that these are version-history entries but adds no format, adjacency, or ordering constraints beyond the schema, so 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 (compares) on a specific resource (two RAP behavior definition versions from its version history) and names the return (unified diff of their sources). This clearly separates it from GetBehaviorDefinitionVersions (list) and GetBehaviorDefinitionVersionSource (single source) without the agent needing to open schemas.

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?

The comparison use case is implied by 'the two ... versions named by content_uri_from and content_uri_to', and batch mode is described, but there is no explicit when-to-use/when-not guidance nor a named alternative such as GetBehaviorDefinitionVersionSource for retrieving a single version.

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