DataSearcher MCP

Overview Schema Source Related Servers Discussions Admin

sync_datahub

Syncs DataHub metadata into a central knowledge base, giving AI assistants consistent context for data analysis and cross-database queries.

Instructions

Синхронизировать метаданные из DataHub в Knowledge Base (ТЗ 1.2).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sync_datahub"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 1, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are present, so the description carries full responsibility for explaining behavior. It discloses only the action and direction, not whether the synchronization overwrites, merges, creates new entries, requires credentials, or is idempotent.

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 a single, front-loaded sentence with the verb at the beginning and no filler. The parenthetical '(ТЗ 1.2)' is a minor spec reference, but overall the description is appropriately concise.

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

Completeness3/5

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

For a zero-parameter tool with an output schema, this is enough to invoke the operation syntactically. However, synchronization semantics such as incremental vs full sync, effect on existing Knowledge Base content, and connection requirements are missing, which is a meaningful gap given there are no annotations.

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?

The input schema has zero properties, so there are no parameters for the description to clarify. Per the baseline for a zero-parameter tool, this is adequate even though no additional parameter detail is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific operation ('synchronize metadata'), a source (DataHub), and a target (Knowledge Base), which makes the tool's purpose identifiable. It does not explicitly differentiate it from sibling tools such as update_metadata or load_dbt, so it stops short of a 5.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives like update_metadata or search_knowledge. There are no stated prerequisites, such as a configured DataHub connection, and no exclusions; the only usage signal is the literal meaning of 'synchronize'.

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