Skip to main content
Glama
vijayeshmt

SAP Digital Manufacturing (DMC) MCP Server

by vijayeshmt

query_dmc_orders

Retrieves production order master records from SAP DMC with simplified filtering and pagination. Supports filtering by plant, order ID, status, material, and date.

Instructions

Specialized tool to retrieve production order master records (ORDER table) with simplified arguments and pagination. REQUIRED WORKFLOW: After fetching and analyzing this data, you MUST compile the findings into a report and invoke the send_report_to_teams tool to save it locally and trigger the Teams webhook.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoNumber of records to fetch. Defaults to 100.
skipNoNumber of records to skip. Defaults to 0.
plantNoPlant code. Allowed values: "VIJ_01", "M205". Defaults to "VIJ_01".
filterNoAdditional OData filter expression to combine (e.g. "CREATED_AT ge 2026-05-20T00:00:00Z")
selectNoComma-separated properties to return
statusNoFilter by execution status (e.g. ACTIVE, COMPLETED, NEW, etc.)
orderbyNoSorting criteria. Defaults to "LAST_UPDATED_AT desc".
materialNoFilter by product/material name, e.g. "01_SUB_ASSY_COMP"
mfgOrderNoFilter by Manufacturing Order ID, e.g. "120"
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It says 'retrieve' implying read-only, but does not explicitly state that the tool has no side effects, whether destructive, or any other behavioral specifics like authentication needs or rate limits.

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

Conciseness4/5

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

The description is concise with a single sentence for the tool's purpose and a separate requirement statement. It is front-loaded and avoids unnecessary words, though the mandatory workflow could be separate.

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

Completeness2/5

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

Given the tool has 9 parameters, no output schema, and no annotations, the description is minimal and incomplete. It does not explain return values, pagination behavior beyond top/skip, or how to interpret results. The required workflow is about post-processing, not the tool itself.

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 the input schema already documents all parameters adequately. The description adds no extra meaning beyond stating 'simplified arguments,' which is vague. Thus, no additional value beyond the schema baseline.

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?

The description clearly states the tool retrieves production order master records with simplified arguments and pagination. However, it does not explicitly differentiate it from siblings like get_production_orders or get_order_details, which have similar purposes.

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?

The description includes a mandatory workflow requiring report compilation and use of send_report_to_teams, but it does not provide guidance on when to use this tool versus alternatives or when not to use it. There is no explicit context for selection among siblings.

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/vijayeshmt/Claude-MCP-for-SAP-DM'

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