Skip to main content
Glama
derekslinz

meta-data-mcp

by derekslinz

Find Providers

opendata_providers_find
Read-onlyIdempotent

Search the plugin registry for open data providers using free-text, domain, or region filters. Returns matching providers and suggests next steps if none are found.

Instructions

Search the meta-data-mcp plugin registry. Returns plugins that match a free-text query and/or domain/region filters. Use this FIRST when you don't know which plugin can answer a question. If no plugin matches, the response includes a next_step field that explains how to autonomously create one via opendata_plugins_create.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of providers to return (1-100, default 20).
queryNoFree-text query. Matched against id, title, description, keywords, domains, regions. Tokens with exact keyword hits score higher.
domainNoRestrict to providers tagged with this domain (e.g. 'health', 'legal', 'finance'). Use opendata_domains_list to enumerate.
regionNoRestrict to providers tagged with this region (e.g. 'us', 'eu', 'uk', 'global'). Use opendata_regions_list to enumerate.
activate_topNoIf > 0, automatically activate the top-N matching providers so their tools become callable in this session. Default 0 means find-providers is read-only — you must call opendata_providers_activate explicitly to load tools.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
no_matchNo
next_stepNo
providersNo
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds that the response includes a `next_step` field for creation guidance, which is a behavioral trait beyond annotations. However, it doesn't mention the activate_top parameter's side effect.

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?

Two sentences, zero waste. All information is front-loaded and each sentence serves a distinct purpose.

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

Completeness4/5

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

Covers purpose, usage, and output (including next_step). Though it omits the activation behavior of the activate_top parameter, the schema covers it. For a search tool with rich schema, this is sufficiently complete.

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 coverage is 100% with detailed parameter descriptions. The description reiterates the free-text query and domain/region filters but adds no new semantic meaning beyond what the schema provides.

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?

Description uses specific verb 'Search' and clearly identifies the resource 'meta-data-mcp plugin registry'. It distinguishes this tool from siblings like opendata_providers_list or opendata_providers_activate by focusing on discovery.

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

Usage Guidelines4/5

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

Explicitly says 'Use this FIRST when you don't know which plugin can answer a question', providing clear entry-point guidance. Also explains fallback to opendata_plugins_create when no match, but doesn't address when to use alternative search or listing tools.

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