mcp-abap-abap-adt-api

searchObject

Read-only

Find ABAP repository objects by name using * wildcard, returning their URI, type, and package. Use the objType filter for quick narrowing; if a filtered search returns no results, retry without the filter to identify the correct type.

Instructions

Find objects by name in the repository, with * as a wildcard - the quickest way from a name to a URI, a type and a package. The objType filter is the quick-search filter of the backend and does not take every sub-type: FUGR/FF answers with an empty list while the unfiltered search returns the module. So when a filter comes back empty, search without it and pick the type from the rows.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "searchObject"
  }
}

Input Schema

Name	Required	Description
`max`	No	Maximum number of results
`query`	Yes	Search query string
`objType`	No	Object type filter

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Sep 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The annotations already declare readOnlyHint and non-destructive behavior, and the description adds substantial behavioral detail beyond them: wildcard support, the backend-filter limitation on subtypes, a concrete FUGR/FF example, and the recommended fallback strategy. This meaningfully informs an agent about quirks that annotations alone would not reveal.

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?

Three sentences, with the core purpose and unique value stated first. Every sentence adds something necessary: the core behavior, the filter quirk, and how to react to empty results. No filler or redundant restatement.

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?

For a read-only search tool with one required parameter and three total, the description covers the purpose, the query semantics, the output result (URI, type, package), and the main failure mode, while the schema covers parameter format. No output schema exists, but the description already states what the user gets from a name. The absence of explicit sibling alternatives is a minor concern given the strong practical guidance.

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 coverage is 100%, so baseline is 3. The description adds extra meaning for query (wildcard semantics) and objType (quick-search filter, subtype limitations), which goes beyond the schema's simple labels. Max is not elaborated, but its schema description already says 'Maximum number of results,' so no major gap remains.

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 uses a specific verb and resource: 'Find objects by name in the repository,' and states the concrete output (URI, type, package). It also calls out the wildcard behavior, which distinguishes this from a plain exact-match search. The 'quickest way from a name to URI/type/package' framing helps differentiate it from sibling search tools.

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

Usage Guidelines4/5

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

The description gives clear guidance on when to use this tool: as the quick way to resolve a name to URI/type/package. It also provides actionable troubleshooting for the objType filter, instructing users to retry without the filter when it returns empty. It does not explicitly name alternatives or exclusion conditions, but the context is strong enough for an agent to choose correctly.

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

Deploy Server