Skip to main content
Glama
AnindyaDR-SAP

mcp-abap-adt

by AnindyaDR-SAP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetTableContents

Retrieve ABAP table data with configurable row limits and line-based pagination for large XML output.

Instructions

Retrieve contents of an ABAP table. max_rows limits SAP rows; startLine/maxLines page the returned textual XML when its serialized size is still large.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxLinesNoMaximum lines to return (1-100000). Omit to request the rest; the byte cap may return fewer lines.
max_rowsNoMaximum number of rows to retrieve
startLineNo1-based line number to start from (default 1). Beyond EOF returns an empty page with hasMore=false.
table_nameYesName of the ABAP table

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.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 behavioral burden. It usefully discloses that output is textual XML, that max_rows limits SAP rows, and that startLine/maxLines page the serialized XML when large. It does not cover errors, auth needs, or exact XML structure, but the core behavior is well communicated.

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 sentences with no filler. The main purpose is front-loaded, and the second sentence concisely explains the key parameter relationships.

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?

Given that there is no output schema and no annotations, the description does a good job explaining the return format (textual XML) and pagination behavior. It is slightly incomplete in not addressing error cases or when the serialized size threshold triggers pagination, but the essentials for a successful call are present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying the distinction between SAP rows (max_rows) and textual XML lines (startLine/maxLines), which would otherwise be ambiguous from the schema alone.

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?

The description states a specific verb and resource: 'Retrieve contents of an ABAP table.' It is clear and distinguishable from sibling tools like GetTable, though it does not explicitly call out that GetTable is for metadata/definition rather than contents.

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

Usage Guidelines2/5

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

No explicit guidance is given about when to use this tool versus alternatives such as GetTable or SearchObject. The description only explains parameter behavior, not selection criteria 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