logic-lab
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 |
|---|---|
| get_manifestA | Return the full Logic Lab art algorithm manifest as a JSON object. |
| search_algorithmsA | Search the Logic Lab manifest for algorithms by keyword, category, or visual intent. |
| get_algorithmA | Return the source text of a Logic Lab .py file or README.md. |
| get_algorithm_summaryA | Return a short summary of a Logic Lab algorithm without fetching full source. |
| search_by_moodA | Search algorithms by creative mood or visual atmosphere. |
| recommend_combinationsA | Suggest multi-layer algorithm combinations for a given artistic intent. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| logic_lab_manifest | Curated manifest of Logic Lab algorithms for search and artwork planning. |
| logic_lab_manifest_summary | Small summary of manifest size, categories, and recommended MCP usage. |
| logic_lab_readme | Top-level README for Logic Lab (falls back to MCP README when installed standalone). |
| logic_lab_mcp_readme | MCP server usage, tools, security notes, and manifest update workflow. |
TDQS
Scored across 6 tools
Each tool has a distinct, well-defined purpose: get_algorithm retrieves source code, get_algorithm_summary returns metadata without source, get_manifest returns the full manifest, search_algorithms searches by keyword, search_by_mood searches by mood, and recommend_combinations suggests combinations. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_algorithm, search_algorithms, recommend_combinations). No mixed conventions or ambiguous names.
With 6 tools, the server is well-scoped for a domain of algorithm discovery and retrieval. Neither too few nor too many; each tool earns its place.
The tool set covers the full lifecycle of algorithm exploration: discovery (search_algorithms, search_by_mood, get_manifest), summary (get_algorithm_summary), full source retrieval (get_algorithm), and even creative combination planning (recommend_combinations). No obvious gaps for a read-only lookup server.