Skip to main content
Glama
derekslinz

meta-data-mcp

by derekslinz

Health Snapshot

opendata_health_snapshot
Read-onlyIdempotent

Check the current health score of data providers, returning a value from 0.0 to 1.0. Scores degrade on recent server or network failures and recover over time.

Instructions

Snapshot the in-memory provider health registry. Returns a score in [0.0, 1.0] for each requested provider (or every registered provider when called without arguments). Health degrades on recent 5xx / 429 / network failures and decays back toward 1.0 over ~5 minutes; 401/403 are excluded as caller misconfig. The discovery app uses this to paint live health badges next to each search result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
provider_idsNoOptional list of provider ids to query. When omitted, returns snapshots for every provider in the static + dynamic registry. Providers with no recorded failures default to a fully-healthy baseline (score 1.0).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
snapshotNo
generated_atNo
Behavior5/5

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

The description adds significant behavioral details beyond annotations: health degrades on 5xx/429/network errors, decays over 5 minutes, excludes 401/403. This complements idempotentHint and readOnlyHint well.

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 concise (3 sentences), front-loaded with the primary action, and every sentence adds value without redundancy.

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 one optional parameter and output schema present, the description fully covers behavior with/without arguments, failure recovery, and use case. No gaps.

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%, and the description adds context: optional provider_ids default to null, behavior when omitted (returns all providers), and baseline score for healthy providers.

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 snapshots the in-memory provider health registry and returns a score per provider, distinguishing it from sibling tools like opendata_providers_list which list providers without health context.

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?

The description explains when to use (to get health scores for one or all providers) and provides business context (painting health badges), but does not explicitly state when not to use or compare to alternatives.

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