Malyn
OfficialServer 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| malynB | Malyn helps with bounded local AI work using shareable Markdown recipes in her Kitchen. Use recipes to discover them, recipe to read one, import_recipe with recipe_file to add a reviewed local Markdown file, and export_recipe to get its shareable filename and Markdown. Import never runs the recipe. An image plus @malyn defaults to describe-my-image; Windows log checks use windows-system-logs. Use models/configure for local model choices and submit with recipe/root/files/images to run. Malyn checks and loads a compatible installed model. check returns report links by default; open or quote reports only when the user asks for details. Use returnMode summary only when requested. Collection steps belong to the supervising agent. Legacy loop actions remain supported. |
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 1 tool
There is only one tool, so nothing can be misselected by name, but the tool internally multiplexes many distinct operations (recipes, recipe, import_recipe, export_recipe, models/configure, submit, check, open, quote, plus legacy loop actions) that an agent must disambiguate purely by reading prose. The boundaries between when to use submit vs. recipe vs. check vs. open are only vaguely stated, making action selection error-prone.
The single tool name 'malyn' is a proper noun, not a verb_noun action name, and the sub-actions referenced inside it mix conventions (snake_case import_recipe/export_recipe, slash-style models/configure and recipe/root/files/images, and free-form verbs like submit, check, open, quote). There is no predictable naming pattern for an agent to generalize from.
The described domain spans recipe discovery, import, export, execution, model configuration, and report retrieval, yet the entire surface is exposed as one mega-tool. That is far too few tools for the apparent scope and forces all routing into a single parameterized entry point.
The underlying lifecycle (discover, read, import, export, configure, run, check/report) arguably exists, but as a single opaque tool none of these operations is independently discoverable or typed, so agents must infer valid action names and parameters from a dense paragraph. This creates real dead-end risk for anything not explicitly enumerated, such as editing or deleting an imported recipe.