Skip to main content
Glama
marianfoo

ARC-1

by marianfoo
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

SAPSearch

Search for ABAP objects by name pattern with wildcards. Perform exact cross-package object lookup via TADIR. Find classes, programs, tables, and more.

Instructions

Search for ABAP objects. Search by name pattern with wildcards (* for any characters). Returns object type, name, package, description, and ADT URI. Use this to find classes, programs, function modules, tables, etc. 2. TADIR lookup (searchType="tadir_lookup"): Exact cross-package object lookup for one or more names via ADT repository quick search. Use this before create/reset workflows instead of long SAPQuery TADIR IN-lists.

Tips: BOR business objects appear as SOBJ type in results. The uri field from results can be used directly with SAPNavigate for references. The objectType field from results can be passed directly to SAPRead/SAPWrite/SAPActivate (ARC-1 auto-normalizes slash suffixes like DDLS/DF, CLAS/OC, PROG/P).

Note: Searches object names only (classes, tables, CDS views, etc.) — field/column names are not searchable here. To find fields by name, use SAPRead(type='DDLS', include='elements') for CDS views or SAPQuery against DD03L.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch pattern for object search, or comma/whitespace-separated names for tadir_lookup.
maxResultsNoMaximum results (default 100)
searchTypeNoSearch mode: "object" (default) searches by object name, "tadir_lookup" does exact cross-package object lookup.
namesNoFor tadir_lookup: exact object names to resolve across packages. Prefer this over long SAPQuery TADIR IN-lists.
objectTypesNoFor tadir_lookup: optional ADT/TADIR type filters (e.g., TABL, DDLS, BDEF, SRVB, CLAS/OC).
objectTypeNoFor source_code search: filter by object type (e.g., PROG, CLAS, FUNC). For tadir_lookup: single type filter; use objectTypes for multiple.
sourceNoFor tadir_lookup only: data source for the lookup. "adt" (default) uses the ADT info-system endpoint — workbench-resolvable objects only. "db" issues SQL against table TADIR — also surfaces orphan/ghost rows from aborted create-delete cycles (requires sql scope and SAP_ALLOW_FREE_SQL=true). "both" runs both paths and adds a "splitBrain" array listing names where the two sources disagree, plus a "warnings" array explaining each divergence (requires sql scope).

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses what the tool returns (object type, name, package, description, ADT URI), mentions that BOR business objects appear as SOBJ, and explains how results can be used with other tools. However, it does not explicitly state that the search is read-only, though that is implied.

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 with sections for general info, search types, tips, and notes. It is front-loaded with the main purpose. While it is fairly long, every sentence adds value, though some details could be more streamlined.

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 absence of an output schema, the description adequately explains the return fields and how to use them. It covers both search modes, parameters, limitations, and integration with other tools. For a search tool with 7 parameters, it provides comprehensive 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%, but the description adds substantial value beyond the schema. It explains the two search types, wildcard usage, the purpose of tadir_lookup, and the source parameter options. Tips like 'uri field from results can be used directly with SAPNavigate' provide rich context.

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: 'Search for ABAP objects.' It specifies two distinct search modes (object and tadir_lookup) and contrasts with sibling tools like SAPRead and SAPQuery, making it easy to understand what the tool does and how it differs.

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 explicit when-to-use and when-not-to-use guidance. For example, it recommends tadir_lookup 'before create/reset workflows instead of long SAPQuery TADIR IN-lists' and notes that field/column names are not searchable, directing users to SAPRead or SAPQuery instead.

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