SAP Digital Manufacturing (DMC) MCP Server

get_legacy_inventory

Retrieve inventory details from legacy SAP ERP via OData v2 filtering by plant, material, and storage location.

Instructions

Get inventory details from legacy SAP ERP via OData v2. Queries with standard OData filtering.

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": {
      "plant": "<plant>"
    },
    "name": "get_legacy_inventory"
  }
}

Input Schema

Name	Required	Description
`plant`	Yes	Plant code, e.g. P001
`material`	No	Material number to filter by
`storageLocation`	No	Storage location code

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 13, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It states OData v2 and filtering but does not explicitly disclose whether the operation is read-only, any authentication or rate limits, or potential side effects. The word "Get" implies read but is not explicit.

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 sentences, both front-loaded with essential purpose and method. No superfluous words or repetition.

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?

The tool has moderate complexity (3 params, 1 required) and no output schema. The description does not indicate return structure (list vs. single) or pagination behavior, which is necessary for an agent to fully understand the tool's usage context.

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% for all three parameters, so baseline is 3. The description adds no additional meaning beyond what the schema already provides (e.g., "standard OData filtering" is generic and not param-specific).

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 verb "Get" and the resource "inventory details" from "legacy SAP ERP via OData v2", making the tool's purpose specific and distinct from siblings like query_dmc_* tools.

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

Usage Guidelines3/5

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

The description implies usage with "Queries with standard OData filtering" but provides no explicit guidance on when to use this tool versus alternatives (e.g., other inventory tools) or any exclusions.

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