Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

get_domain

Retrieve the definition of a DDIC domain from an SAP system by providing the domain name and optional system ID.

Instructions

Fetch DDIC domain definition from SAP system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDomain name (e.g. MATNR)
system_idNoSAP system ID (e.g. DEV). Omit to use default system.

Implementation Reference

  • Registration of the 'get_domain' tool in the ListToolsRequestSchema handler, defining its name, description, and input schema (requires a 'name' string property for the domain name).
    {
      name: "get_domain",
      description: "Fetch DDIC domain definition from SAP system",
      inputSchema: {
        type: "object" as const,
        properties: { name: { type: "string", description: "Domain name (e.g. MATNR)" }, ...SYSTEM_ID_PROP },
        required: ["name"],
      },
    },
  • Handler for the 'get_domain' tool in the CallToolRequestSchema switch statement. Parses the domain name from args, calls client.getSourceOrMetadata with ADT URIs for domain source/main and metadata, and returns the result.
    case "get_domain": {
      const { name: domName } = NameSchema.parse(args);
      const encoded = encodeURIComponent(domName.toUpperCase());
      const result = await client.getSourceOrMetadata(
        `/sap/bc/adt/ddic/domains/${encoded}/source/main`,
        `/sap/bc/adt/ddic/domains/${encoded}`
      );
      return { content: [{ type: "text", text: result }] };
    }
  • The getSourceOrMetadata helper method on AdtClient. Tries to fetch the source (text/plain) at the sourcePath, and if a 404 occurs, falls back to fetching metadata at the metadataPath.
    async getSourceOrMetadata(sourcePath: string, metadataPath: string): Promise<string> {
      try {
        return await this.getSource(sourcePath);
      } catch (error: unknown) {
        if (axios.isAxiosError(error) && error.response?.status === 404) {
          return await this.getMetadata(metadataPath);
        }
        throw error;
      }
    }
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., read-only, auth requirements, side effects). It only states the basic action.

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 a single concise sentence, no redundant information.

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?

Given the simplicity of the tool and lack of output schema, the description is minimally adequate but lacks context on how this tool relates to similar ones (e.g., what a DDIC domain is) and does not compensate for missing annotations.

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 coverage is 100%, so the schema fully describes the two parameters. The description does not add extra meaning beyond what the schema provides.

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 'Fetch' and clearly identifies the resource 'DDIC domain definition from SAP system'. It distinguishes from sibling tools like get_data_element or get_structure.

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 this tool versus alternatives like get_data_element or get_table. No prerequisites or exclusions mentioned.

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