Skip to main content
Glama
derekslinz

meta-data-mcp

by derekslinz
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Create Plugin

opendata_plugins_create

Creates a new open-data plugin from a YAML spec, registers it immediately, and opens a contribution PR.

Instructions

Autonomously create a new plugin for this meta-data-mcp server from a YAML spec. Use this when opendata_providers_find returned no match. Recommended flow: first call opendata_plugins_draft with structured fields to get a valid YAML spec, then pass it here. The new plugin is materialized to disk, imported, registered in the live registry, and its tools become available immediately. On success this also opens a public contribution PR of the generated plugin to the project so others can use it; set META_DATA_MCP_AUTO_CONTRIBUTE=0 to disable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainsNoRegistry domains for the new plugin (e.g. ['security']). Use `opendata_domains_list` to see existing values, but new domain names are allowed.
regionsNoRegistry regions for the new plugin (e.g. ['global', 'us']). Use `opendata_regions_list` to see existing values.
keywordsNoSearch keywords that should match this plugin.
spec_yamlYesFull YAML spec for the new plugin. Must include id, server_name, base_url, description, homepage, and at least one tool. See tools/specs/example_weather_alert.yaml for the canonical form.
license_noteNoOptional short licensing/attribution note for the data source.
requires_envNoNames of any environment variables the new plugin needs (e.g. API keys). Leave empty for keyless APIs.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Adds significant behavioral context beyond annotations: materialization to disk, import, registration, immediate availability, and auto PR. Annotations only indicate destructiveHint=false, so description adds value without contradiction.

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?

Concise paragraph with each sentence adding value: purpose, when to use, recommended flow, effects, and configuration hint. No redundancy or 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?

Complete coverage given tool complexity: describes side effects, prerequisite flow, and configuration. References other tools for context. No output schema needed.

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

Parameters3/5

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

Schema covers all 6 parameters with descriptions (100% coverage), so baseline is 3. The description does not add extra parameter-specific details beyond what's in the schema.

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 clearly states the tool creates a new plugin from a YAML spec, specifies the verb 'create' and resource 'plugin', and distinguishes from siblings by referencing opendata_providers_find and opendata_plugins_draft.

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?

Explicitly states when to use the tool ('when opendata_providers_find returned no match') and provides a recommended flow involving opendata_plugins_draft, plus mentions environment variable to disable auto-contribution.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/derekslinz/meta-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server