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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetBehaviorDefinitionVersions

Lists the version history of a RAP behavior definition by name, including version IDs, authors, timestamps, titles, transport requests, and content URIs.

Instructions

[read-only] Lists the version history of the RAP behavior definition named by behavior_definition_name: each version with its versionId, author, updatedAt, title, the transportRequest (and transportDescription) that produced it when available, and the opaque content_uri that names the version's source. 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": {
      "behavior_definition_name": "<behavior_definition_name>"
    },
    "name": "GetBehaviorDefinitionVersions"
  }
}

Input Schema

NameRequiredDescriptionDefault
behavior_definition_nameYesRAP behavior definition name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv8.5.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are present, so the description carries the full load, and it does well: it declares the tool read-only via the [read-only] tag, labels content_uri as opaque, notes transport fields are only present 'when available', and explains the non-obvious recordable batch semantics (empty content in batch, answer read by number afterwards). It stops short of describing ordering or pagination of versions.

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?

Front-loaded with the read-only tag and the core action, followed by the return-field enumeration and the batch caveat. The field list is somewhat long but each item is informative; no filler sentences.

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?

With no output schema and no annotations, the description compensates by enumerating the response fields and explaining batch behavior, which is what an agent needs to call and interpret it. Only minor gaps remain (version ordering, size of result sets).

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 single parameter has 100% schema description coverage ('RAP behavior definition name'), so the schema already does the work. The description restates the name parameter without adding format, case-sensitivity, or lookup guidance, so the baseline 3 applies.

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?

States a specific verb and resource: lists the version history of a RAP behavior definition, and even enumerates the per-version fields returned (versionId, author, updatedAt, transportRequest, content_uri). This clearly separates it from GetBehaviorDefinitionVersionDiff and GetBehaviorDefinitionVersionSource in practice, though no sibling is named explicitly.

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?

Usage is implied by the purpose (use it to inspect version history), and the batch-mode sentence gives practical guidance on calling it inside BatchBegin/BatchEnd. However, there is no explicit statement of when to prefer this over the Diff/Source siblings, and no prerequisites or exclusions.

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