Skip to main content
Glama
kajalkhairnarsap

mcp-abap-adt

by kajalkhairnarsap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetTypeInfo

Read-onlyIdempotent

Retrieve ABAP type information with pagination options to handle large result sets.

Instructions

Retrieve ABAP type information. For large results, use startLine/maxLines to page through it instead of retrieving it all at once.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive, so the description does not need to repeat that. It adds useful context that results can be large and that pagination is available. The schema's maxLines note already covers the byte-cap truncation behavior, and nothing contradicts the annotations.

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 first establishes purpose and the second adds a concrete usage tip. The information is front-loaded and every clause earns its place.

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 simple read-only lookup with one required parameter and a well-documented schema, the description is largely sufficient. The main gaps are the lack of detail about what the returned 'type information' contains and no differentiation from sibling tools, but the current definition still enables a competent agent to invoke it correctly.

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%, with each parameter already documented, including paging semantics and EOF behavior. The description reinforces the pagination message but does not add parameter-level meaning beyond what the schema already provides.

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 'Retrieve ABAP type information', which provides a clear verb and resource. It does not explicitly distinguish it from sibling getters like GetStructure or GetTable, but the 'ABAP type' phrasing narrows the target enough to be recognizable.

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?

The description gives explicit guidance for large results: use startLine/maxLines to page instead of retrieving everything at once. It does not discuss when to choose this tool over alternatives, but the pagination when/when-not guidance is clear and practical.

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