Skip to main content
Glama
arc-mcp

ARC-1

by arc-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

SAPSearch

Read-only

Search ABAP objects by name pattern with wildcards, resolve exact object-directory (TADIR) entries across packages, or find source code. Use optional type filters to narrow results.

Instructions

Search for ABAP objects, exact object-directory entries, or source code. Modes:

  1. Object search (default): name pattern with wildcards (*); returns type, name, package, description, ADT URI.

  2. TADIR lookup (searchType="tadir_lookup"): exact cross-package lookup of one or more names (prefer over long SAPQuery TADIR IN-lists). Tips: BOR objects appear as SOBJ; the uri field feeds SAPNavigate, objectType feeds SAPRead/SAPWrite/SAPActivate. Searches object NAMES only — for field names use SAPRead(type='DDLS', include='elements') or SAPQuery on DD03L.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namesNoFor tadir_lookup: exact object names to resolve across packages. Prefer this over long SAPQuery TADIR IN-lists.
queryNoSearch pattern for object search, or comma/whitespace-separated names for tadir_lookup.
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).
maxResultsNoMaximum results (default 100)
objectTypeNoObject search: SAP-side type filter before the result limit (e.g., UIAC, CLAS, CLAS/OC). Source search: type filter (e.g., PROG, CLAS, FUNC). For tadir_lookup: single type filter; use objectTypes for multiple.
searchTypeNoSearch mode: "object" (default) searches by object name, "tadir_lookup" does exact cross-package object lookup.
objectTypesNoFor tadir_lookup: optional ADT/TADIR type filters (e.g., TABL, DDLS, BDEF, SRVB, CLAS/OC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • changedInput schema / properties / objectType / description
      Previous value: -"For source_code search: filter by object type (e.g., PROG, CLAS, FUNC). For tadir_lookup: single type filter; use objectTypes for multiple."New value: +"Object search: SAP-side type filter before the result limit (e.g., UIAC, CLAS, CLAS/OC). Source search: type filter (e.g., PROG, CLAS, FUNC). For tadir_lookup: single type filter; use objectTypes for multiple."
    • addedInput schema / properties / objectType / maxLength
      Added value: +64
  2. Changed1 schema field changedv1.0.2
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv0.9.6
  4. Removedv0.9.3
  5. First observedv0.6.4

TDQS

A4.9/5.0
Behavior5/5

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

The readOnlyHint annotation is already present, but the description adds substantial behavioral detail: the two search modes, default behavior, BOR-as-SOBJ mapping, return fields, and the differences among adt/db/both TADIR sources including splitBrain/warnings and the SQL-scope prerequisite. This goes well beyond the annotation.

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

Conciseness5/5

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

The description is dense but every sentence earns its place: mode definitions, output fields, sibling routing, and gotchas are all decision-relevant. The length is justified by seven parameters and multiple modes, and the main purpose is front-loaded.

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?

For a tool with no output schema, it does well: object-search return fields are listed, TADIR source divergence is explained, and security prerequisites are mentioned. The main gap is that the first sentence advertises source-code search and objectType references a 'Source search', but the Modes list only defines object and tadir_lookup, leaving the agent to infer how source-code search is triggered.

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 real cross-parameter meaning: it explains how searchType selects a mode, how names and query differ by mode, how objectType changes meaning between object and source search, and what source='both' produces. The parameter descriptions alone would not convey this integration.

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 opens with a specific verb and resource ('Search for ABAP objects, exact object-directory entries, or source code') and then names two distinct modes with different inputs and outputs. It also differentiates from siblings behaviorally by explaining that uri feeds SAPNavigate and objectType feeds SAPRead/SAPWrite/SAPActivate.

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 explicitly says when to prefer TADIR lookup over long SAPQuery TADIR IN-lists, and it redirects field-name searches to SAPRead(type='DDLS', include='elements') or SAPQuery on DD03L. This is concrete when-to-use vs. when-not-to-use guidance, not just a vague hint.

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

Deploy Server

Other Tools