Skip to main content
Glama
doris-mcp

doris-mcp

by fhm0520

doris_get_query_profile

Read-onlyIdempotent

Retrieves the execution profile for a previously run Doris query ID, helping diagnose performance or failures; returns not found when the query ID has no stored profile.

Instructions

取某个查询的 profile(SHOW QUERY PROFILE "/id")。只对执行过的 query id 有效, 取不到时 Doris 返回 1105 not found。

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": {
      "query_id": "<query_id>"
    },
    "name": "doris_get_query_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
query_idYesquery id,可从当前查询或日志里拿

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description only needs to add behavior the schema cannot. It does so usefully by disclosing the failure mode — Doris returns error 1105 not found — which tells the agent how a miss manifests. Retention/availability rules for profiles after a query finishes are not mentioned.

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, front-loaded with purpose and the underlying command, followed by the validity constraint and error outcome. Nothing is redundant or padded.

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, return structure need not be described, and the one parameter is fully documented. Purpose, precondition, and failure mode are all covered; only profile retention/availability behavior is missing, a minor gap for this complexity level.

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 description coverage is 100%, with the query_id parameter documented as coming from the current query or logs, so the schema already carries the semantics. The description adds only the constraint that the id must correspond to an executed query, which is useful but marginal; baseline 3 applies.

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 verb and resource ("取某个查询的 profile") and anchors it to the concrete backend command SHOW QUERY PROFILE "/id", so an agent knows exactly what will be executed. It does not name a sibling tool such as doris_explain_query as an alternative, so it stops short of full differentiation.

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 states the key precondition plainly: the tool is only valid for query ids that have actually executed, implying that a plan-only or unknown id will fail. It does not explicitly say when to prefer this over sibling diagnostics like explain or execute, but the usage context is clear.

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