Skip to main content
Glama
I772104

mcp-abap-adt

by I772104
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

GetCDSViewContents

Query CDS view data with filtering, pagination, parameters, and batch mode. Retrieve specific columns, apply WHERE conditions, sort results, and run up to five queries in a single call.

Instructions

Query CDS view data with filtering, pagination, parameter support, and batch queries. Either provide view_name for a single query, or provide queries array for batch mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoOptional: Number of rows to skip for pagination (default: 0). Warning: CDS views recalculate on each query.
columnsNoOptional: Specific columns to retrieve (default: all columns). Column names are validated against view metadata.
queriesNoOptional: Batch mode - execute multiple queries in one call (max: 5 for CDS views, omit when using view_name). Each query supports all single-query parameters.
max_rowsNoOptional: Maximum number of rows to retrieve (default: 100, max: 500)
order_byNoOptional: Column names for sorting results. Column names are validated against view metadata.
view_nameNoName of the CDS view (required for single query mode, omit when using queries array)
parametersNoOptional: CDS view parameters as key-value pairs (e.g., {"p_date": "2024-01-01"})
where_conditionsNoOptional: WHERE conditions for filtering. Simple: {"SalesOrderType": "OR"}. Advanced: {"SalesOrderType": {"eq": "OR"}}. Note: ADT Data Preview API only supports equality (=) operator.
include_column_metadataNoOptional: Include column type and description in response (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It adds pagination and batch-mode context, but omits the read-only nature, the result-size ceiling behavior, or the batch cap (max 5) — those constraints live only in the schema, so the description's own behavioral disclosure is thin.

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?

Two tightly written sentences: capability summary first, then the mode-selection rule. Zero filler and front-loaded.

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

Completeness3/5

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

Covers the mode-selection logic adequately, but with no output schema and nested batch objects, the description says nothing about the shape of results (or how batch results are keyed by id). For a 9-parameter tool with nested structures, this leaves a real gap.

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 schema already documents all nine parameters in detail (e.g., the max 500 rows, max 5 batch limit, ADT equality-only note). The description adds marginal value by clarifying the view_name vs queries selection rule, which the schema only implies.

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 (query) and resource (CDS view data) plus the supported capabilities (filtering, pagination, parameters, batch). This clearly distinguishes it from the sibling GetCDSView (metadata retrieval), though it never names that sibling to reinforce the distinction.

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

Usage Guidelines4/5

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

Explicitly defines the two modes and their mutual exclusion: 'Either provide view_name for a single query, or provide queries array for batch mode.' Clear operational context, but no guidance on when to prefer batch over repeated single calls, nor any exclusions relative to GetCDSView/ExportCDSViewToFile.

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