Skip to main content
Glama
AnindyaDR-SAP

mcp-abap-adt

by AnindyaDR-SAP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetFunction

Retrieve ABAP function module source code. Use startLine and maxLines to page through large modules instead of fetching all at once.

Instructions

Retrieve ABAP Function Module source code. For large function modules, use startLine/maxLines to page through the source 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.
function_nameYesName of the function module
function_groupYesName of the function group

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden; it reveals that retrieval can be large and supports paging via startLine/maxLines. However, it doesn't mention output format, errors, or that this is a read-only operation, leaving behavior partially implicit.

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, no filler; purpose is front-loaded and the paging guidance follows immediately. Every sentence 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 retrieval tool with fully documented parameters, the description covers the essential behavior and paging strategy. It does not describe the return structure, but the tool's output (source code) is largely implied by the purpose.

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 parameters. The description adds a usage hint (paging for large modules) but doesn't add meaning beyond the parameter descriptions.

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?

The description states 'Retrieve ABAP Function Module source code' with a specific verb and resource, clearly differentiating it from sibling tools like GetFunctionGroup and GetProgram. Even though the name is generic, the description pins down exactly what is returned.

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?

It gives an explicit usage condition: for large function modules, use startLine/maxLines rather than retrieving everything at once. This is clear context, though it doesn't discuss choosing among sibling 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