Draft Spec
opendata_plugins_draftBuild a validated YAML plugin spec from structured inputs, ensuring correct id format, tool names, and parameter consistency before creating the plugin.
Instructions
Build a validated YAML plugin spec from structured inputs. Use this BEFORE opendata_plugins_create to avoid hand-writing YAML. Validates id format, kebab-case tool names, path-placeholder/param consistency, parameter types, and response format. Returns the YAML string ready to feed into opendata_plugins_create.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Plugin id in snake_case, e.g. 'global_nvd_cve'. Becomes the Python module name under meta_data_mcp/providers/. | |
| title | Yes | Human-readable title for the registry entry. | |
| tools | Yes | At least one tool definition. Each becomes one MCP tool on the server. | |
| domains | No | Registry domains (e.g. ['security', 'government']). | |
| regions | No | Registry regions (e.g. ['global', 'us']). | |
| base_url | Yes | API base URL with no trailing slash (e.g. 'https://services.nvd.nist.gov'). | |
| homepage | Yes | URL to the API documentation or provider homepage. | |
| keywords | No | Search keywords that should match this plugin in opendata_providers_find. | |
| description | Yes | One- or two-sentence description of what this plugin covers. | |
| server_name | No | kebab-case server name for the plugin registry entry. Defaults to id with underscores replaced by hyphens. | |
| requires_env | No | Names of environment variables this API needs (e.g. ['NVD_API_KEY']). |