Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

search_object

Search ABAP repository objects by name pattern using wildcards. Specify max results and optional system ID to locate development objects in SAP systems via ADT API.

Instructions

Search for ABAP repository objects by name pattern. Supports wildcards (*) for partial matches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query (e.g. Z_MY* or CL_ABAP*)
max_resultsNoMaximum results to return (default: 100)
system_idNoSAP system ID (e.g. DEV). Omit to use default system.

Implementation Reference

  • The actual implementation of searchObject in the AdtClient class. It performs an HTTP GET request to the SAP ADT repository information system search API with a query string and optional maxResults parameter, returning the raw XML response.
    async searchObject(query: string, maxResults = 100): Promise<string> {
      const response = await this.http.get<string>(
        `/sap/bc/adt/repository/informationsystem/search?operation=quickSearch&query=${encodeURIComponent(query)}&maxResults=${maxResults}`,
        { headers: { Accept: "*/*" }, responseType: "text" }
      );
      return response.data;
    }
  • Zod schema (SearchObjectSchema) defining the input validation for the search_object tool: required 'query' string and optional 'max_results' number.
    const SearchObjectSchema = z.object({
      query: z.string(),
      max_results: z.number().optional(),
    });
  • Registration of the 'search_object' tool in the ListTools handler, defining its name, description, and input schema properties (query, max_results, system_id).
    {
      name: "search_object",
      description: "Search for ABAP repository objects by name pattern. Supports wildcards (*) for partial matches.",
      inputSchema: {
        type: "object" as const,
        properties: {
          query: { type: "string", description: "Search query (e.g. Z_MY* or CL_ABAP*)" },
          max_results: { type: "number", description: "Maximum results to return (default: 100)" },
          ...SYSTEM_ID_PROP,
        },
        required: ["query"],
      },
    },
  • The tool invocation handler for 'search_object' in the CallToolRequest handler. It parses args via SearchObjectSchema and calls client.searchObject(query, max_results), returning the result as text content.
    case "search_object": {
      const { query, max_results } = SearchObjectSchema.parse(args);
      const results = await client.searchObject(query, max_results);
      return { content: [{ type: "text", text: results }] };
    }
Behavior2/5

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

No annotations provided, so description carries full burden. Discloses wildcard support but does not state read-only nature, required permissions, or result format.

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?

Two concise sentences front-loaded with key action and resource. No wasted words.

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

Completeness3/5

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

Adequate for a search tool: explains purpose, wildcards, and optional system_id. Lacks output details and result limits behavior beyond max_results.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. Description reiterates wildcard support but adds minimal value beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Search for ABAP repository objects by name pattern' with wildcard support. Verb and resource are specific, but does not explicitly differentiate from sibling 'get_*' tools that retrieve specific objects.

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

Usage Guidelines2/5

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

No guidance on when to use versus alternatives like get_class or get_table. Lacks context on prerequisites or use cases.

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/ethanhan2014/sap-adt-mcp'

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