Skip to main content
Glama
kajalkhairnarsap

mcp-abap-adt

by kajalkhairnarsap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetFunction

Read-onlyIdempotent

Retrieve ABAP function module source code. Use startLine and maxLines to page through large modules and avoid overwhelming responses.

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds behavioral context about paging and the byte cap potentially returning fewer lines, which is useful beyond the schema.

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 waste. The core purpose is front-loaded, and the paging guidance is concise and actionable.

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 read-only retrieval tool with full schema coverage and no output schema, the description covers the essential usage. The paging behavior is explained, and the annotations cover safety. Minor gap: no mention of what the response format looks like, but that's not required without an output schema.

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 the paging strategy context but doesn't add new parameter semantics beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the tool retrieves ABAP Function Module source code, with a specific verb and resource. It distinguishes itself from siblings like GetFunctionGroup and GetProgram by naming the exact artifact type.

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 provides explicit guidance for large function modules: use startLine/maxLines to page through source. It doesn't explicitly name alternatives or when not to use it, but the paging guidance is clear usage context.

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