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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetDdlVersionSource

Read the DDL source of a specific CDS view version by content_uri from its version history to inspect or compare historical view definitions.

Instructions

[read-only] Reads the source of the CDS view (DDL source) version named by content_uri, an entry of the CDS view (DDL source)'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": "GetDdlVersionSource"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_uriYesOpaque content_uri of a version, from the CDS view (DDL source)'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 GetDdlVersions entry."New value: +"Opaque content_uri of a version, from the CDS view (DDL source)'s version history."
  2. Addedv8.5.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the safety burden itself by declaring [read-only]. It also discloses the non-obvious batch/recordable semantics — the call returns empty content and must be read back by number — which an agent could not infer from schema. It omits error behavior for invalid or stale content_uri.

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 front-loaded sentences with the read-only marker and the core action up front. The repeated parenthetical 'CDS view (DDL source)' is slightly redundant but does not obscure meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A single-parameter read tool with no output schema: the description says it returns the source, and explains the empty-content batch case, which is the one place the return value deviates. Nothing needed to call it correctly is missing.

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 describes content_uri as an opaque URI from the version history. The description restates the same provenance without adding format, sourcing, or validity details beyond it, 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 and resource: reads the DDL source of a named CDS view version, not the version list or diff. The distinction from siblings like GetDdlVersions and GetDdlVersionDiff is implicit in the phrasing and unambiguous.

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 indicates that content_uri is an entry of the version history, which implies you must first enumerate versions, but no sibling (e.g. GetDdlVersions) is named and there are no explicit exclusions for when not to use it.

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