Skip to main content
Glama
marianfoo

ARC-1

by marianfoo
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

SAPNavigate

Read-only

Find definitions, references, hierarchies, and get code completion in ABAP code. Filter where-used results by object type for targeted analysis.

Instructions

Navigate code: find definitions, references (where-used), code completion, and class hierarchy. Use for "go to definition", "where is this used?", "what does this class inherit?", and auto-complete. For references: uses the full scope-based Where-Used API returning detailed results with line numbers, snippets, and package info. Optional objectType filter narrows results to a specific ADT type in slash format (e.g., CLAS/OC, PROG/P). Type+name params are auto-normalized (e.g., type="clas" works). For hierarchy: returns superclass, implemented interfaces, and direct subclasses via SEOMETAREL. You can use type+name instead of uri (e.g., type="CLAS", name="ZCL_ORDER") for a where-used list without needing the full ADT URI.

For CDS entities (DDLS), prefer SAPContext(action="impact") — it returns the same where-used data pre-classified into RAP buckets (projection views, BDEFs, SRVDs, access controls, metadata extensions, documentation, ABAP consumers), which answers "what breaks if I change this view" directly without manual bucketing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesNavigation action
uriNoSource URI of the object. Optional for references if type+name are provided.
typeNoObject type (PROG, CLAS, INTF, FUNC, etc.) — alternative to uri for references.
nameNoObject name — alternative to uri for references.
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.
lineNoLine number (1-based)
columnNoColumn number (1-based)
sourceNoCurrent source code (for definition/completion)

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

The description discloses behavioral traits such as the Where-Used API returning detailed results, auto-normalization of type+name, and behavior of objectType filter on older systems. It does not contradict the readOnlyHint annotation.

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 well-structured and front-loaded with the main purpose. It is somewhat lengthy but each sentence adds value, covering multiple actions and caveats without significant redundancy.

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?

Given the complexity of 8 parameters with many optional combinations and no output schema, the description thoroughly explains how to use each parameter, return values for references, and provides alternative tool guidance. It is fully complete for the tool's domain.

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?

With 100% schema description coverage, the baseline is 3. The description adds value by explaining auto-normalization, the effect of objectType on older systems, and the alternative use of type+name instead of URI, going beyond the 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's purpose: 'Navigate code: find definitions, references, code completion, and class hierarchy.' It uses specific verbs and resources, and differentiates from sibling tools by advising when to use SAPContext instead (for CDS entities).

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?

Explicit guidance on when to use each action (definition, references, completion, hierarchy) and a direct recommendation to prefer SAPContext for CDS entities, providing clear alternatives and when-not-to-use scenarios.

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