Skip to main content
Glama

ALM X++ MCP Server

by io.github.alimbenhelal-pro
OverviewDiscussionsAdmin

dmf

Idempotent

Consolidated Data Management Framework tool — one entry point for all 5 DMF operations, selected via action. Each action forwards to the exact same implementation as its dedicated tool (dmf_import_file / dmf_create_data_project / dmf_apply_entity_filter / dmf_export_package / dmf_get_job_status) — identical behavior and validation, just one tool schema instead of five. The dedicated tools remain available unchanged.

action="import" (= dmf_import_file): entityName, legalEntity, filePath OR csvContent, definitionGroupId?, execute?, overwrite?, pollTimeoutSeconds? action="create_project" (= dmf_create_data_project): projectName, entities, sourceName, operationType? ('Export' default or 'Import') action="apply_filter" (= dmf_apply_entity_filter): projectName, entityRowName, aotEntityName, fieldName, filterValue action="export" (= dmf_export_package): definitionGroupId, legalEntity, packageName?, reExecute?, pollTimeoutSeconds? action="status" (= dmf_get_job_status): executionId

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesimport | create_project | apply_filter | export | status
executeNoimport: execute after staging. Default true.
entitiesNocreate_project: comma-separated DMF entity names.
filePathNoimport: path to a .csv file on disk (or use csvContent).
fieldNameNoapply_filter: field to filter on, e.g. 'VendorAccountNumber'.
overwriteNoimport: overwrite existing project definition. Default true.
reExecuteNoexport: re-execute the project. Default true.
csvContentNoimport: inline CSV content (or use filePath).
entityNameNoimport: target DMF entity name, e.g. 'Customers V3'.
sourceNameNocreate_project: existing DMF source data format name.
executionIdNostatus: the executionId returned by an import or export action.
filterValueNoapply_filter: value or wildcard to match.
legalEntityNoimport/export: legal entity / company id, e.g. 'USMF'.
packageNameNoexport: optional package name.
projectNameNocreate_project/apply_filter: DMF project name.
aotEntityNameNoapply_filter: AOT entity name, e.g. 'VendVendorV2Entity'.
entityRowNameNoapply_filter: entity row label, e.g. 'Vendors V2'.
operationTypeNocreate_project: 'Export' (default) or 'Import'.
definitionGroupIdNoimport/export: definitionGroupId (DMF project id).
pollTimeoutSecondsNoimport/export: max seconds to poll for completion. Default 300.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

It discloses important behavior beyond annotations: action routing to identical implementations, per-action parameter groups, optionality markers, defaults like execute/overwrite/reExecute, and the use of executionId for status polling. It does not describe return values or failure behavior, but annotations already establish the read/write/destructive profile.

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?

Despite covering five operations and 20 parameters, the description is well-structured and front-loaded. Each action gets one compact line listing its parameters, and the introductory sentence establishes the purpose without wasted words.

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

Completeness4/5

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

For a consolidated tool with 20 parameters, no output schema, and annotations available, this description is very complete: it covers all five operations, their dedicated-tool equivalences, and relevant defaults. The main remaining gap is that it does not describe return or status-response shapes, but the action mapping and executionId hint mitigate this.

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 the schema already documents each parameter. The description adds meaning by grouping parameters by action, marking optionality inline, and clarifying key relationships such as filePath OR csvContent, executionId from import/export, and operationType defaulting to 'Export'.

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 opening sentence clearly states this is a consolidated entry point for all five DMF operations and explicitly lists them. It also distinguishes itself from the dedicated sibling tools by saying it forwards to the exact same implementation with identical behavior and validation.

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 explicit action values and maps each one to its dedicated tool, so an agent knows exactly which action to select for a given operation. It notes the dedicated tools remain available unchanged, but does not explicitly state when one should prefer the consolidated tool over a dedicated one.

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

All ALM X++ MCP Server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources