Skip to main content
Glama
Sign In
PLS-MCP Server

PLS-MCP Server

by sweet-dog-cyber
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_departments

list_departments
Read-onlyIdempotent

Retrieve the organizational tree structure of departments, optionally filtered by name. Returns nested hierarchy with details like code, manager, and sub-departments.

Instructions

【📊 查询】获取部门树状组织结构。

参数:

  • keyword: 部门名称关键词（可选）

返回: 部门树结构，含名称、编码、负责人、电话、子部门

提示: 最多返回 2000 条。返回为嵌套树结构。

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

Input Schema

NameRequiredDescriptionDefault
keywordNo按部门名称搜索

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations indicate read-only, idempotent, non-destructive behavior. The description adds that it returns up to 2000 records as a nested tree structure, which is useful beyond annotations. No contradictions.

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 description is concise and uses structure (emojis, bullet points). It front-loads the purpose and provides key details without unnecessary verbosity.

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?

For a simple list tool with one optional parameter and clear return structure described, the description is complete enough. No output schema exists, but the description outlines return fields.

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 single parameter 'keyword' is described in both the schema and description as an optional search term. The description adds context (optional, keyword search) beyond the schema's '按部门名称搜索'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name and description clearly state the tool retrieves a tree structure of departments. The emoji and Chinese text indicate a query operation. It is distinct from sibling tools like list_personnel or list_tags.

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?

The description does not explicitly state when to use this tool versus alternatives, but the context of sibling tools suggests it is for department listings. No when-not-to-use guidance is provided.

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

Deploy Server

Other Tools