Skip to main content
Glama
musharna

data-aggregator-mcp

by musharna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_sources

Read-only

Lists wired data sources with their layers, filters, auth needs, rate limits, and status; optionally probes health for key sources via check_health.

Instructions

List wired data sources and their capabilities (layer, kinds, supported filters, auth requirement, rate limit, status).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
check_healthNoWhen true, probe 5 sources (zenodo, datacite, omics, literature, huggingface) and attach a 'health' field ({status: up|down, latency_ms, detail}) to those entries; every other source gets health: null. Default false: returns the static catalog with no network.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourcesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.54.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv0.42.0
    • changedInput schema / properties / check_health / description
      Previous value: -"When true, probe 5 sources (zenodo, datacite, omics, literature, huggingface) and attach a 'health' field ({status: up|down, latency_ms, detail}) to those entries; the remaining 7 sources get health: null. Default false: returns the static catalog with no network."New value: +"When true, probe 5 sources (zenodo, datacite, omics, literature, huggingface) and attach a 'health' field ({status: up|down, latency_ms, detail}) to those entries; every other source gets health: null. Default false: returns the static catalog with no network."
  3. Changed1 schema field changedv0.40.0
    • changedInput schema / properties / check_health / description
      Previous value: -"When true, probe each source's base endpoint and attach a 'health' field ({status: up|down, latency_ms, detail}) to each source. Default false: returns the static catalog with no network."New value: +"When true, probe 5 sources (zenodo, datacite, omics, literature, huggingface) and attach a 'health' field ({status: up|down, latency_ms, detail}) to those entries; the remaining 7 sources get health: null. Default false: returns the static catalog with no network."
  4. Changed1 schema field changedv0.16.0
    • addedInput schema / properties / check_health
      Added value: +{
+  "default": false,
+  "description": "When true, probe each source's base endpoint and attach a 'health' field ({status: up|down, latency_ms, detail}) to each source. Default false: returns the static catalog with no network.",
+  "type": "boolean"
+}
  5. First observedv0.11.0

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds the shape of the catalog entries, which is mild value, but it does not disclose the default no-network behavior or the targeted health-probe side effects — that context lives only in the parameter schema. With annotations and an output schema present, the bar is lower and a 3 fits.

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?

A single dense sentence that front-loads the action and resource, then lists the returned fields parenthetically. No filler, no redundancy.

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?

Annotations cover the safety profile, the output schema covers the return shape, and the sole parameter is fully described, so the description need not repeat them. It is essentially complete for a read-only lister, missing only the positioning relative to sibling tools.

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_description_coverage is 100% and the single check_health parameter is fully documented in-schema, including which five sources get probed and what the health field contains. The description contributes nothing about the parameter, so the baseline 3 applies.

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?

States a specific verb ("List") and resource ("wired data sources") and enumerates exactly what each entry contains (layer, kinds, supported filters, auth requirement, rate limit, status). No sibling (search, resolve, fetch, operate, relate) performs catalog enumeration, so the tool is clearly distinguishable.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the discovery step that should precede search/fetch, but the description never says so, nor does it state when not to call it (e.g., prefer search when you already know the source). No alternative routing is given.

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

Deploy Server

Other Tools