Skip to main content
Glama
doris-mcp

doris-mcp

by fhm0520

doris_list_udfs

Read-onlyIdempotent

Lists user-defined functions in Doris with pagination, optional database context, and name-pattern filtering. Returns total count, page items, and next offset for browsing UDFs.

Instructions

列出 UDF,分页返回。

    SHOW FUNCTIONS 在 1.2 不支持 LIMIT,也不支持 SHOW GLOBAL FUNCTIONS(语法错误),
    且要求连接已选库;因此取回后在本地切页(UDF 数量有限,代价可忽略)。

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

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

Input Schema

NameRequiredDescriptionDefault
limitNo本页返回条数
offsetNo跳过条数,用于翻页
databaseNo可选,库上下文;1.2 的 SHOW FUNCTIONS 要求连接已选库
name_likeNo可选,函数名 LIKE 模式

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: pagination happens client-side after a full fetch because the server-side LIMIT is unsupported, the cost is characterized as negligible, and the database-context requirement is disclosed. This is exactly the kind of non-obvious behavior an agent would otherwise not anticipate.

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 a single clause, followed by a short rationale block and a compact return shape. The enumerated return fields are somewhat redundant given an output schema exists, costing a bit of space, but the overall length is proportionate and every other sentence carries useful constraint information.

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 covering safety and an output schema covering the return payload, the description supplies the remaining missing piece: the server-side pagination limitation and the database-context prerequisite. An agent has enough to call this correctly; only the absence of guidance on when to prefer an alternative (e.g. raw query) keeps it from full marks.

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 description coverage is 100%, so the baseline is 3. The description earns one extra point because it clarifies that limit/offset are applied locally rather than pushed to the server, which changes what an agent should expect from those parameters when composing paging calls. It does not add syntax detail for name_like or database beyond what the schema already states.

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 opening line states a specific verb and resource ('列出 UDF') plus the delivery mode ('分页返回'), so an agent knows immediately this is a paginated listing of user-defined functions. It is unambiguous against siblings like doris_list_tables or doris_list_databases by resource name, though it never explicitly contrasts with doris_execute_query, which could also run SHOW FUNCTIONS.

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 context is implied rather than stated: the description explains the backend limitation (SHOW FUNCTIONS in 1.2 lacks LIMIT and requires a selected database), which tells the agent why this tool exists instead of raw SQL. However, it gives no explicit when-to-use/when-not-to-use rule and names no alternative tool for cases where the full function list or different filtering is needed.

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