Skip to main content
Glama

SAPLint

Check ABAP and CDS source code quality using local abaplint rules that automatically select cloud or on-premises rules based on system type.

Instructions

Run local abaplint rules on ABAP and CDS source code. System-aware: auto-selects cloud or on-prem rules based on detected system type.

Actions:

  • "lint": Check source for issues. Returns errors and warnings. Works for ABAP (PROG, CLAS, INTF, FUNC) and CDS views (DDLS) — catches syntax errors, naming conventions, field order, legacy view patterns.

  • "lint_and_fix": Lint + auto-fix all fixable issues (keyword case, obsolete statements, etc.). Returns fixed source.

  • "list_rules": List all available rules with current config. No source needed.

  • "format": Pretty-print ABAP source via SAP's ADT formatter (uses the SAP system's global formatter settings). Requires source. Returns the formatted source.

  • "get_formatter_settings": Read the SAP system's global PrettyPrinter settings (indentation, keyword style). No params.

  • "set_formatter_settings": Update the SAP system's global PrettyPrinter settings. Requires indentation (bool) and/or style (keywordUpper|keywordLower|keywordAuto|none). Blocked in read-only mode.

For server-side checks (ATC, syntax check, unit tests), use SAPDiagnose instead. Note: lint/lint_and_fix/list_rules run locally; format/*_formatter_settings call the SAP system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesCheck type
sourceNoABAP or CDS source code to lint/format (not needed for list_rules/get_formatter_settings)
nameNoObject name (used for filename detection)
indentationNoPrettyPrinter: indent source (for set_formatter_settings)
styleNoPrettyPrinter: keyword casing (for set_formatter_settings)
rulesNoRule overrides: { "rule_name": false } to disable, { "rule_name": { "severity": "Warning" } } to configure. Overrides system defaults.
Behavior4/5

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

Annotations indicate not read-only or destructive. Description adds context: local vs system calls, read-only mode blocking set_formatter_settings. Could elaborate on side effects of format/set, but sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Structured with bullet points for actions, each sentence adds value. Slightly verbose but not excessive. Could be more concise, but well-organized.

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?

Covers all actions, parameter dependencies, and sibling differentiation. No output schema, but return values are briefly described. Adequate for complexity.

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 has 100% coverage with descriptions. Description adds action-specific parameter usage (e.g., source not needed for list_rules). Enhances understanding beyond schema.

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 runs local abaplint rules on ABAP and CDS source code, listing specific actions. It distinguishes from sibling SAPDiagnose, which is for server-side checks.

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

Usage Guidelines5/5

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

Explicitly says when to use this tool vs alternatives: 'For server-side checks (ATC, syntax check, unit tests), use SAPDiagnose instead.' Also describes system-aware behavior for rule selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/marianfoo/arc-1'

If you have feedback or need assistance with the MCP directory API, please join our Discord server