MCP server exposing Simulator.Company REST API operations as tools for managing actors, graph-based business processes, form templates, financial accounts, and visualizations
Critical gaps across all dimensions. 52 tools lack visible input schemas in source code, cannot verify parameter types, descriptions, or constraints. Tool descriptions are present but minimal (10-50 chars typical), providing insufficient context for LLM selection. No evidence of output schema documentation. Error handling is absent, no recovery guidance, categorization, or actionable messages. Naming is inconsistent: verb_noun mostly present but some tools like 'existLink', 'massLink', 'pruneLongEdges' are unclear or non-standard. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite 15+ destructive operations. Security concerns: login/set-workspace/set-environment tools expose auth state management as tool parameters rather than server-side injection. Composition issues: 52 tools is excessive; many could be consolidated (e.g., createActor/createActors, getActor/searchActors, createAccount/updateAccount/deleteAccount). No pagination, no batch operation guidance, no chaining IDs in responses.
Link attachments to an actor
Add an account to a form template
Build a link to a Simulator UI view
Auto-layout actors with domain-clustering strategy
Create an account for an actor
Define an account name (asset, liability, expense, income)
Create a single actor (node) in a layer
No input schemas visible in source code for any of 52 tools. Cannot verify parameter types, constraints, or descriptions.
Tool descriptions are minimal (10-50 chars), below the 194-char baseline for production tools. Descriptions lack WHEN to use, prerequisites, or state-modification warnings. E.g., 'Create a single actor (node) in a layer' omits what fields are required, what the return value contains, or how it chains with other tools.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | 2026-07-28+ | v2 |
Bulk-create up to 50 actors in a single call
Create a chart/dashboard actor on a layer
Create a currency for financial tracking
Create a new form template
Create a link (edge) between two actors
Create a reaction for an actor
Delete an account
Delete an actor from a layer
Delete an edge
Delete a link between actors
Check if a link exists between two actors
Discover saved skill playbooks (Skills-form actors) by intent
Get access rules for an object
Get accounts for an actor
Get actor details by ID
Get attachments for an actor
Get links for an actor
Enumerate all actors on a layer in one call
Get available currencies
List all available form templates
Get actors linked to a given actor
Get reactions for an actor
Get actors related to a given actor
Load a saved skill playbook in full by slug (ref) or id
Get available workspaces
Authenticate with Simulator.Company via OAuth2 browser flow
Create, update, or delete a layer
Create multiple links in one call
Move actors on a layer canvas
Delete links that exceed a Manhattan distance threshold
Export a layer to a local YAML file for editing
Sync a local YAML graph file back to a Simulator layer
Read an attachment file
Unlink attachments from an actor
Save access rules for an object
Search actors by title or custom fields
Set environment profile (local or prod) for API calls
Save workspace ID to .env for subsequent API calls
Update an account
Update actor properties (title, description, status)
Update edge properties
Update an existing form template
Set an actor's avatar from URL, local file, or base64 (auto SVG→PNG)
Bulk-upload actor pictures with SHA-256 deduplication
Upload a file as base64
No error handling or recovery guidance. Tools like deleteActor, pruneLongEdges, and deleteLink are destructive but provide no confirmation, dry-run, or error categorization.
Auth state management exposed as tool parameters (login, set-workspace, set-environment) instead of server-side secret injection. Use server-side secret injection via environment variables or vault.'
52 tools is excessive and violates single-responsibility principle. Many tools could be consolidated: createActor/createActors, getActor/searchActors, createAccount/updateAccount/deleteAccount.