Data Platform MCP

by 1franky

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

hello_world

Verifies MCP connectivity via a deterministic greeting, confirming the Data Platform server is reachable.

Instructions

Return a deterministic greeting used to verify MCP connectivity.

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": "hello_world"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No		world

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.0Aug 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses a behavioral trait ('deterministic'), implying consistent output and no side effects, but it does not explicitly state read-only behavior, error conditions, or what happens without parameters. For a trivial tool this is acceptable but minimal.

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, front-loaded sentence conveys the tool's purpose and key behavior. No wasted words; every element earns its place.

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?

The tool is simple, and the output schema exists, so return values need not be described. However, the parameter 'name' is unexplained, and the description does not clarify whether the greeting changes based on it. This minor omission prevents a higher score.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate for the single 'name' parameter. The description never mentions the parameter or how it affects the greeting, leaving users to guess. This is a significant gap.

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's function with a specific verb ('Return'), a resource ('a deterministic greeting'), and its purpose ('verify MCP connectivity'). This distinguishes it uniquely from all sibling tools, which are data-related.

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 explicitly states the context for use: 'used to verify MCP connectivity.' It does not mention alternatives or exclusions, but the purpose is unambiguous. Given that sibling tools like health_check and test_connection might overlap, a brief note on when to prefer this tool would have earned a 5.

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