Skip to main content
Glama
doris-mcp

doris-mcp

by fhm0520

doris_list_databases

Read-onlyIdempotent

Lists Doris databases with paging support via limit and offset, returning total counts and next-page offsets so you can browse catalogs easily.

Instructions

列出数据库,分页返回。

    internal:走 information_schema.schemata(1.2 的 SHOW DATABASES 不支持 LIMIT,
    这里在服务端分页);指定其他 catalog 时用 SHOW DATABASES FROM,取回后本地切页。

    返回:{ok, total, count, offset, limit, items[{name}], has_more, next_offset, source}
    

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

Input Schema

NameRequiredDescriptionDefault
limitNo本页返回条数
offsetNo跳过条数,用于翻页
catalogNo可选,catalog 名;默认当前 catalog(internal)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and open-world behavior, so the description is free to add real context: Doris 1.2's SHOW DATABASES lacks LIMIT, forcing server-side pagination for internal and local slicing for other catalogs. That is genuine behavioral detail an agent could not derive from annotations; the only weakness is that the return-shape line partially repeats the output schema.

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?

The purpose is front-loaded in the first line, followed by a compact implementation note and a return summary. The explicit field listing for the return object is somewhat redundant given the output schema exists, but no sentence is confusing 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 annotations, full schema descriptions, and an output schema all present, the description is complete enough: it explains pagination semantics for both execution paths and points to has_more/next_offset for continuation. Minor gaps such as whether empty or system databases are included, or required privileges, do not block correct invocation.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by tying the catalog parameter to concrete semantics: default is the current catalog (internal) and switching catalogs changes both the query used and where pagination happens. It does not add format examples for limit/offset, but that is already covered by the schema.

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 opens with a specific verb and resource ('list databases, paginated return') and explains the two execution paths (internal schema vs. other catalog). This is clear enough for an agent to know exactly what the tool does, though it never explicitly contrasts itself with siblings such as doris_list_catalogs or doris_list_tables.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent learns that passing 'internal' or omitting catalog triggers server-side pagination while another catalog triggers SHOW DATABASES FROM with local paging. There is no explicit when-to-use/when-not-to-use guidance or routing to alternative tools, which leaves the choice between this and doris_list_catalogs to inference.

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