Skip to main content
Glama

SAPNavigate

Read-only

Navigate SAP ABAP code: find definitions, references with scope-based where-used (line numbers, snippets, package), code completion, and class hierarchy. Filter references by ABAP object type.

Instructions

Navigate code: definitions, references (where-used), completion, class hierarchy. references uses the scope-based Where-Used API (line numbers, snippets, package); optional objectType filters by ADT slash type (e.g. CLAS/OC, PROG/P); pass type+name instead of uri. hierarchy returns superclass + interfaces + direct subclasses. For CDS (DDLS), prefer SAPContext(action="impact") — the same where-used pre-classified into RAP buckets, answering "what breaks if I change this view".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriNoSource URI of the object. Optional for references if type+name are provided.
lineNoLine number (1-based)
nameNoObject name — alternative to uri for references.
typeNoObject type (PROG, CLAS, INTF, FUNC, etc.) — alternative to uri for references.
actionYesNavigation action
columnNoColumn number (1-based)
sourceNoCurrent source code (for definition/completion)
objectTypeNoFor references action: filter where-used results by ADT object type in slash format (e.g., PROG/P, CLAS/OC, FUGR/FF, INTF/OI). On systems supporting the scope endpoint, only returns references from objects of the specified type. On older systems, the filter is ignored and all references are returned with a note.
Behavior5/5

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

Annotations declare readOnlyHint=true, consistent with a read-only navigation tool. The description adds significant behavioral details: references returns line numbers/snippets/package, explains objectType filter behavior on older/scope-supporting systems, and describes hierarchy output (superclass, interfaces, subclasses). No contradictions.

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?

The description is front-loaded with the core actions and is reasonably efficient, though the sentence about references and objectType could be slightly more concise. Overall, every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 8 parameters and no output schema, the description thoroughly covers all actions, edge cases (older systems), and provides guidance for CDS. Required parameters (action) are clear, and optional parameters are explained with usage context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with individual parameter descriptions, but the description adds further context: explains that type+name can substitute uri for references, clarifies the objectType filter's system-dependent behavior, and notes source is required for definition/completion. All parameters are semantically enriched.

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 explicitly lists the navigation actions (definitions, references, completion, hierarchy) and distinguishes from sibling SAPContext for CDS impact analysis. It uses specific verbs and resources.

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?

The description provides when-to-use guidance for each action, including the optional objectType filter for references and explicitly recommends SAPContext for CDS impact analysis, handling when-not conditions.

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/arc-mcp/arc-1'

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