MCP Tools
All current tools are declared as Model Context Protocol (MCP) tools in soplangAgent/mcp-config.json and executed through the same command entrypoint: /code/soplang-tool.sh.
These tools are consumed through Ploinky MCP routing and mostly operate on SOPLang workspace state.
Current Tool Matrix
| Tool Name | Plugin Method | Purpose |
|---|---|---|
sync_markdown_documents |
SoplangBuilder.syncMarkdownDocuments |
Parse markdown docs and synchronize templates into SOPLang workspace. |
execute_workspace_build |
SoplangBuilder.executeWorkspaceBuild |
Run workspace build pipeline after sync. |
get_variables_with_values |
SoplangBuilder.getVariablesWithValues |
Return variable objects enriched with resolved values. |
get_variable_with_value |
SoplangBuilder.getVariableWithValue |
Return one variable by documentId and varName. |
get_commands |
SoplangBuilder.getCommands |
List registered SOPLang commands in current workspace. |
get_types |
SoplangBuilder.getCustomTypes |
List registered custom SOPLang types. |
execute_skill |
AchillesSkills.executeSkill |
Execute one discovered Achilles skill by name. |
Input Contracts
Most tools currently use empty schemas. The two explicit argument contracts are get_variable_with_value, which requires documentId and varName, and execute_skill, which requires skillName with optional promptText.
{
"name": "execute_skill",
"inputSchema": {
"skillName": { "type": "string", "optional": false },
"promptText": { "type": "string", "optional": true }
}
}Execution Characteristics
Tool calls can be queued asynchronously at AgentServer level where "async": true is configured. Every invocation starts with isolated process state and fresh plugin bootstrap, and wrapper failures propagate as MCP-visible errors when the process exits non-zero.