lampa-mcp-server

Overview Schema Source Related Servers Discussions Admin

Generate Lampa plugin, setting, or hook text

scaffold_plugin

Read-onlyIdempotent

Generate copy-paste Lampa plugin scaffolds as markdown: full main.js, SettingsApi snippets, or matching Listener/Player hooks. Provide required inputs to get a complete starting point.

Instructions

Returns markdown only; does not write the repository — not a patch against existing files (draft_patch). kind=plugin emits a full main.js scaffold: requires plugin_name + description; plugin_kind (screen default | player | context-menu | settings-only) applies only here. kind=setting emits a SettingsApi registration snippet: requires key + label + type (type=toggle aliases trigger). kind=hook emits the best-matching Listener/Player hook: requires trigger. A missing required combo for the chosen kind errors instead of returning a partial scaffold. Follow up with validate_code mode=plugin on the result.

Input Schema

TableJSON Schema

Name	Required	Description
`key`	No	For kind=setting: Storage key, e.g. 'myplugin_enabled'. Prefix with plugin name.
`kind`	Yes	plugin=full main.js scaffold; setting=SettingsApi snippet; hook=Listener catalog.
`type`	No	For kind=setting: param type. toggle aliases trigger.
`label`	No	For kind=setting: human-readable UI label.
`options`	No	For kind=setting type=select: option ids.
`trigger`	No	For kind=hook: event or lifecycle moment, e.g. 'player start', 'app ready', 'card full'.
`component`	No	For kind=setting: Settings section id. Defaults to key prefix before '_'.
`description`	No	For kind=plugin: one-sentence description of what the plugin does.
`plugin_kind`	No	For kind=plugin: screen (default) \| player \| context-menu \| settings-only.
`plugin_name`	No	For kind=plugin: snake_case folder/id, e.g. 'my_feature'.
`default_value`	No	For kind=setting: default value.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`markdown`	Yes	Human-readable markdown report. Always present, including empty-result cases. Does not write files.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.6.0Sep 4, 2026

TDQS

A5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Even though annotations already mark the tool as read-only and idempotent, the description adds valuable behavioral detail: it returns markdown only, errors on missing required combinations, and offers best-matching hook selection. These are operational traits an agent needs that annotations do not fully convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but well-structured, front-loading the safety-critical fact that it does not write files before explaining each kind. Every sentence carries actionable information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists and annotations cover safety, the description completes the picture by specifying required parameter combos, error behavior, and the recommended follow-up validation step. An agent can correctly invoke this tool across all three kinds without further clarification.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds crucial grouping semantics by kind, required parameter combinations, and the toggle/trigger alias. It explains that plugin_kind applies only to kind=plugin, which is not clear from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear statement that the tool returns markdown and does not write the repository, then defines the three distinct kinds of scaffold output. It explicitly distinguishes itself from draft_patch, so an agent can tell which tool produces text versus patches.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit per-kind guidance: which parameters are required, when plugin_kind applies, and that validate_code should be used as a follow-up. It also states when this tool is not appropriate by naming draft_patch, making the decision boundaries clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server