Skip to main content
Glama
Sign In
data-aggregator-mcp

data-aggregator-mcp

by musharna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

relate

Read-only

Identify how 2-10 resource IDs connect before joining: return metadata-level hints from shared accessions, cross-identifiers, explicit links, and version lineage.

Instructions

Given 2-10 resource ids, return metadata-level join/harmonization HINTS: how the datasets relate and on what key they could be joined. Detects shared accessions (BioProject/SRA/GEO), shared cross-identifiers (doi/pmid/pmcid), explicit links between the inputs, and version lineage. Tool names in this text are this server's own; your client may list them with a prefix (in Claude Code, mcp__data-aggregator__resolve): call the name it lists. HINTS ONLY — it does not read file columns, fetch files, or execute any join/merge/conversion; each hint names the shared value as evidence. Resolve ids first if you only have a search result. Per-id resolve failures are reported, not fatal.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ids": "<ids>"
    },
    "name": "relate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes2-10 source-prefixed resource ids to relate.

Output Schema

NameRequiredDescriptionDefault
noteNo
hintsNo
errorsNo
resolvedYes
input_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.54.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. Addedv0.43.0
  3. Removedv0.42.0
  4. Addedv0.40.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and the description does not contradict that — it reinforces it by stating no files are fetched and no joins are executed. Beyond the annotation it discloses that each hint names the shared value as evidence, and that per-id resolve failures are reported rather than fatal, which is exactly the kind of partial-failure behavior an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core contract (inputs, output kinds) before caveats, and every sentence carries information. The client-prefix aside about mcp__data-aggregator__resolve is useful but slightly peripheral, keeping it just short of a 5.

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?

An output schema exists, so return values need not be described, and the description still characterizes what hints contain (join key plus the shared value as evidence). Combined with the failure-isolation note and the resolve prerequisite, an agent has everything needed to call this correctly and interpret results.

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

Parameters4/5

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

Schema coverage is 100% and the schema documents the 2-10 range and 'source-prefixed resource ids,' so the description's job here is small. It still reinforces the count bound and the source-prefixed requirement, making the format constraint harder to miss than in schema alone.

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 (relate) plus the exact input shape (2-10 resource ids) and the output class (metadata-level join/harmonization hints), then enumerates the signal types it detects (shared accessions, cross-identifiers, explicit links, version lineage). This is clearly distinct from siblings like resolve and fetch, which return records rather than relationships.

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 scopes use: 'HINTS ONLY — it does not read file columns, fetch files, or execute any join/merge/conversion,' which tells the agent when-not-to-use. It also gives a prerequisite ('Resolve ids first if you only have a search result') naming the correct sibling, so the ordering against resolve is unambiguous.

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