Export ABAP function groups directly to .fugr.abap files in the tmp folder. Automatically converts the function group name to the Z-namespace during export.
Export an ABAP function group from the system directly to a file in the tmp folder with .fugr.abap extension. Automatically converts function group name to Z-namespace.
| Name | Required | Description | Default |
|---|---|---|---|
| function_group | Yes | Name of the ABAP function group to export |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does disclose two useful behaviors: the output location/extension and the automatic Z-namespace name conversion. It is silent on overwrite behavior for an existing file, permission requirements, and failure modes, which are material for a tool that writes to disk.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no filler, and the primary action plus output destination are front-loaded before the secondary namespace-conversion note. Every clause carries information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema and no annotations exist, so the description must cover behavior alone. It adequately explains what gets produced and where, but leaves an agent unsure about return value, overwrite semantics, and error conditions for a write-to-disk operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single parameter is self-explanatory, so the baseline is 3. The description does add one piece of parameter-relevant meaning beyond the schema: that the supplied function group name is converted to the Z-namespace, so the value passed may not match the file name written.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Export) and resource (ABAP function group) plus the exact artifact produced: a file in the tmp folder with a .fugr.abap extension. This distinguishes it from GetFunctionGroup/GetFunction, which retrieve objects rather than writing them to disk.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'directly to a file' implies the export-to-disk use case versus retrieving content via GetFunctionGroup, but no explicit when-to-use or when-not-to-use guidance is given, nor any precondition such as the group needing to exist or the caller needing authorization.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.