Skip to main content
Glama
doris-mcp

doris-mcp

by fhm0520

doris_get_runtime_capabilities

Read-onlyIdempotent

Check supported SQL syntax and runtime capabilities for the current Doris instance before writing queries to avoid unsupported or hanging features; enable probe for live spot checks.

Instructions

返回当前实例的能力矩阵(1.2 实测结论):哪些语法可用、哪些会挂死或不存在。 写 SQL 前先查一次,能避免用 2.0+ 语法踩坑。probe=true 时附带实时抽查结果。

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_get_runtime_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
probeNo是否额外跑几条廉价语句做实时抽查

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety is covered. The description adds genuinely new context beyond those: the matrix reflects '1.2 实测结论' (empirically verified against a specific version), and probe=true triggers live spot-checks, which tells the agent the default result is static/version-scoped rather than freshly measured. It does not discuss cost or latency of probing, but that is a minor gap given annotation coverage.

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?

Three short sentences, front-loaded with the purpose before the usage advice and the probe note. No filler or redundant restatement of the name. It is appropriately sized for a lightweight introspection tool.

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?

With an output schema present, the description need not describe the matrix's structure, and it correctly focuses on scope (version-1.2 empirical findings) and the one behavioral toggle. An agent has enough to decide to call it before authoring SQL. A note on the relative cost of probing would make it complete.

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 coverage is 100% with a single optional parameter, and the schema already explains that probe runs a few cheap statements for live verification. The description's 'probe=true 时附带实时抽查结果' largely mirrors that, adding only the consequence that the output includes the spot-check results. With the schema doing the heavy lifting, the baseline 3 is appropriate.

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 and resource: it returns the current instance's capability matrix, listing which syntax constructs are usable versus which hang or do not exist. That is far more informative than the title '能力矩阵', and the phrase '写 SQL 前先查一次' implicitly separates it from execution-oriented siblings such as doris_execute_query. It stops short of explicitly naming a sibling, so a 4 rather than 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 Guidelines4/5

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

It gives a concrete trigger: query this once before writing SQL to avoid 2.0+ syntax pitfalls. That is clear when-to-use guidance tied to a real workflow. There is no explicit when-not-to-use clause or named alternative, which keeps it below a 5.

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