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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetMetadataExtensionVersionSource

Reads the source of a specific CDS metadata extension version identified by content_uri, enabling inspection of historical metadata extension definitions without modifying the system.

Instructions

[read-only] Reads the source of the CDS metadata extension version named by content_uri, an entry of the CDS metadata extension'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": "GetMetadataExtensionVersionSource"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_uriYesOpaque content_uri of a version, from the CDS metadata extension'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 GetMetadataExtensionVersions entry."New value: +"Opaque content_uri of a version, from the CDS metadata extension's version history."
  2. Addedv8.5.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a genuinely non-obvious trait: in batch mode the call is recorded under the next number and returns empty content, read back later by number. The '[read-only]' tag plus this recordable semantics is meaningful context beyond structured data.

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 before the batch/recordable caveat. Dense but no filler; the second sentence earns its place by covering batch semantics.

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 with no output schema, the description covers purpose, provenance of the identifier, and batch return behavior, which is the main surprise an agent would hit. Only the shape of the returned source text is left implicit.

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 single parameter is already documented as an opaque content_uri from the version history. The description restates essentially the same thing, adding no format, example, or origin detail 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.

Purpose4/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 source of a CDS metadata extension version identified by content_uri. It is distinguishable from GetMetadataExtensionVersions/VersionDiff by the word 'source' and the requirement for a version content_uri, though it never names those siblings 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?

Implies the prerequisite (content_uri is 'an entry of the CDS metadata extension's version history'), which hints the agent must first enumerate versions. But it never names GetMetadataExtensionVersions as the way to obtain that uri, and gives no when-not guidance versus the diff or versions tools.

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