Skip to main content
Glama
Sign In
GAIIA Expert Proxy (MCP Server)

GAIIA Expert Proxy (MCP Server)

by dapooleygmailcom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gaiia_start_process

Start a BPMN process instance using a registered blueprint slug with optional custom payload data.

Instructions

Starts/triggers an instance of a registered BPMN process blueprint with an optional custom payload.

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": {
      "process_type": "<process_type>"
    },
    "name": "gaiia_start_process"
  }
}

Input Schema

NameRequiredDescriptionDefault
process_typeYesThe unique processType/slug of the BPMN blueprint (e.g. driver-roster-change)
payloadNoOptional custom JSON payload context for the process run

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations; description does not disclose side effects, such as whether the call is asynchronous, idempotent, or what state changes occur. For a trigger action, this is insufficient.

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

Conciseness3/5

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

Single sentence, no fluff, but lacks enough detail to be efficiently informative. Could be improved with more context.

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 2 params, no output schema, no annotations, the description is incomplete. Missing error behavior, success indication, or execution mode (sync/async).

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%; the description repeats the payload's optional nature but adds no new meaning. Baseline 3 is appropriate.

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 'starts/triggers' and the resource 'registered BPMN process blueprint', and mentions the optional payload. It effectively distinguishes from siblings like gaiia_list_processes.

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?

No guidance on when to use this tool vs alternatives. Missing prerequisites (e.g., process blueprint must exist) and when not to use.

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

Deploy Server

Other Tools