Skip to main content
Glama
doris-mcp

doris-mcp

by fhm0520

doris_ping

Read-onlyIdempotent

Checks Doris database connectivity and returns version, default database, server time, and result limit—use it as the first step in connection troubleshooting.

Instructions

检查连通性并返回 Doris 版本、默认库、服务器时间与结果限制。连通性排查的第一步。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description's list of returned fields largely duplicates the output schema, and it says nothing about latency, cost, or failure behavior — with annotations doing the heavy lifting, this is a modest addition.

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?

Two short sentences, both front-loaded: the capability statement first, the workflow position second. Nothing is redundant or padded.

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?

For a zero-parameter diagnostic with a full output schema and complete annotation coverage, the description supplies everything an agent needs: what it checks, what it returns, and when to reach for it first.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The schema is an empty object, consistent with a no-argument ping.

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 states a specific verb+resource ('检查连通性') and enumerates what the call returns: Doris version, default database, server time, and result limits. No sibling tool does a connectivity check, so the agent can distinguish it on function alone, though no sibling is named explicitly.

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?

'连通性排查的第一步' gives clear when-to-use context, positioning this as the entry point of a diagnostic sequence. It does not state when to skip it or name a follow-on alternative, but the intended triggering situation is unambiguous.

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