Appian MCP Server

create_procurement_request

Submit a structured procurement form payload to Appian to initiate a multi-step procurement workflow process.

Instructions

Submits a completely structured multi-step procurement form payload directly into Appian to start the workflow process.

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": {
      "procurementRequest": "<procurementRequest>"
    },
    "name": "create_procurement_request"
  }
}

Input Schema

Name	Required	Description	Default
`procurementRequest`	Yes	The complete hierarchical JSON mapping all fields from the procurement form.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 17, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are present, so the description carries full burden. It states that the tool starts a workflow, but lacks details on side effects (e.g., whether it is idempotent, permission requirements, or error behavior). This is insufficient for a mutation tool.

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, well-formed sentence that conveys the core action without any redundant words. It is appropriately front-loaded.

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 complexity of a nested parameter and no output schema, the description should clarify what the tool returns (e.g., a request ID) or the outcome after submission. It only describes the input and action, leaving the return behavior unspecified.

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 baseline is 3. The description adds that the payload is 'completely structured' and 'multi-step', but does not provide further meaning beyond the schema's object definition.

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 'submits' and the resource 'a completely structured multi-step procurement form payload', with the target 'into Appian to start the workflow process'. It distinguishes from siblings like create_labelling_request, which likely handles a different form type.

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 when a procurement request needs to be created, but provides no explicit guidance on when to use this tool versus alternatives (e.g., create_labelling_request), nor does it mention prerequisites or when not to use it.

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

Deploy Server