transformatron
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_startA | Start the local transform server and wait until it answers. Args: ssl: Serve over HTTPS. Requires generate_certs first. Both the Maltego desktop client and the Graph Browser require it. |
| server_stopB | Stop the running transform server. |
| server_restartA | Restart the server to pick up new or edited transform modules. Args: ssl: Serve over HTTPS after restarting. Left unset, the scheme the server is already running under is preserved, so reloading an HTTPS server keeps the Maltego desktop client working. |
| server_statusA | Report whether the server is running, healthy, and how many transforms it serves. |
| server_logsA | Return recent server log output. Args: lines: Number of trailing log lines to return. |
| list_transformsA | List every transform the running server advertises, with input and output types. An output type of NONE means the transform function is missing a return annotation, which stops the Maltego client from routing to it. |
| get_transformA | Return the full detail document for one transform. Args: transform_id: Fully qualified transform name from list_transforms. |
| list_entitiesA | List the entity types the running server advertises. |
| run_transformA | Run a transform against one input entity and return its results. Check the reported entity count: a transform can report success while producing nothing. See docs/transform-authoring.md. Args: transform_id: Fully qualified transform name from list_transforms. entity_type: Maltego type of the input entity, e.g. maltego.Domain. entity_value: Value carried by the input entity. settings: Optional transform settings, keyed by setting name. timeout: Seconds to wait before cancelling the run. |
| get_seed_urlA | Return the seed URL and the steps to register this server with Maltego. |
| generate_certsA | Generate a self-signed certificate for serving over HTTPS. Args: force: Overwrite an existing certificate pair. |
| scaffold_transformA | Scaffold a new Maltego transform module from a cURL command or OpenAPI specification. Args: service: Optional service name slug (e.g. 'greynoise', 'threatfox'). curl: A full cURL command string demonstrating an API request. openapi: An OpenAPI/Swagger spec string or file path. sample_response: Optional sample JSON response string to infer output fields. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct action: server lifecycle, transform metadata, execution, or setup. There is no overlap between get_transform and run_transform, nor between the server_* commands.
Most tools follow a verb_noun pattern (get_transform, list_entities, run_transform), while server management tools use a server_ prefix (server_start, server_stop). This is a minor stylistic deviation but still predictable and readable.
12 tools is well within the ideal range for a server management and transform toolkit. Each tool serves a clear purpose without redundancy, covering discovery, execution, and server control.
The surface covers the full server lifecycle (start/stop/restart/status/logs), transform introspection (list/get), execution (run), and setup (seed URL, certs, scaffold). No essential operations are missing for the domain.