aris-mcp

Aris Import Canonical Workflow

aris_import_canonical_workflow

Read-onlyIdempotent

Convert canonical workflows to EPC records and AML text while listing EPC representation losses; no repository writes occur.

Instructions

Convert a canonical workflow to EPC records and AML text, listing what EPC cannot express as losses. Writes nothing to the repository.

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": {
      "canonical": "<canonical>"
    },
    "name": "aris_import_canonical_workflow"
  }
}

Input Schema

Name	Required	Description	Default
`strict`	No	Refuse PROCESS_EXPORT_LOSSY instead of exporting when EPC cannot express a construct.
`canonical`	Yes	A medulla.process.canonical/v1 document.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.0Nov 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavioral context: the result enumerates constructs EPC cannot express as losses, and non-persistence is confirmed in prose rather than left to the hints. It stops short of explaining what a lossy result looks like or how it surfaces PROCESS_EXPORT_LOSSY.

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 short sentences with no filler, and the transformation is front-loaded ahead of the non-persistence guarantee. Every clause carries information.

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?

With an output schema present, return values need no explanation, and the description covers the transformation, the loss report, and the absence of side effects. Only the caller-side decision of when to pick this over a sibling tool is left unaddressed.

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% and both parameters are documented in the schema, including the strict flag and the medulla.process.canonical/v1 document type. The description's mention of losses gives thematic context for strict but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: convert a canonical workflow into EPC records and AML text, plus a loss report. It also distinguishes itself from the ingest/import siblings by declaring 'Writes nothing to the repository', so an agent can tell what it is not.

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 phrase 'writes nothing to the repository' implies a preview/dry-run use case and implicitly separates it from aris_import_aml, but the description never explicitly names when to choose this over aris_export_canonical_workflow or aris_import_aml. Usage is only inferable, not stated.

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

Deploy Server