Skip to main content
Glama
Can-Y
by Can-Y

explore

Explore PDM objects: list block resources, retrieve field details, report and reset properties using various actions.

Instructions

统一探索入口,通过 action 参数选择子功能。

Actions: block_resources(block) 列出指定 Block 的资源名称。 block_summaries(block) 列出指定 Block 的汇总表名称。 resource_info(block, resource) 获取 Block 资源的字段名和记录名。 resource_defaults(block, resource) 获取 Block 资源的默认值。 resource_valid_values(block, resource, fields) 获取 Block 资源字段的有效值范围。fields 逗号分隔,留空获取所有。 summary_info(target, summary) 获取汇总表的字段名、记录名和当前值。target 为 "project" 或 block 名。 list_property(target) 列出 PDM 对象的属性名。target 为 "project" / block名 / "block.resource"。 report_property(target, pattern, all_props, detail) 报告 PDM 对象的属性。pattern 支持通配符和正则。 reset_property(target, prop) 重置 PDM 对象的属性为默认值。

Args: action: 操作名(见上方列表)。 block: Block 名称(block_* / resource_* 操作使用)。 resource: 资源名称(resource_* 操作使用)。 fields: 字段名,逗号分隔(resource_valid_values 使用)。 summary: 汇总表名称(summary_info 使用)。 target: 目标对象,"project" / block名 / "block.resource"。 pattern: 属性名匹配模式(report_property 使用)。 all_props: 是否报告所有属性(report_property 使用)。 detail: 是否报告详细帮助信息(report_property 使用)。 prop: 要重置的属性名(reset_property 使用)。 session_id: 目标会话 ID。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propNo
blockNo
actionYes
detailNo
fieldsNo
targetNoproject
patternNo*
summaryNo
resourceNo
all_propsNo
session_idNodefault

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It details each action's behavior and parameters, though it does not cover side effects, auth requirements, or rate limits. Still, it provides adequate transparency for an exploration tool.

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 well-structured with a clear intro and a bullet-style list of actions. It is longer but each sentence adds value. Could be slightly more concise, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (11 parameters, multiple actions), the description is comprehensive. It covers all actions and parameters clearly. An output schema exists, so return values are not needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining each parameter's purpose in the context of each action. For example, block is used in block_* actions, resource in resource_* actions, and fields valid values.

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 description clearly states it is a unified exploration entry point with sub-functions selected by action parameter. Each action is explicitly listed with its purpose, distinguishing it from sibling tools that have different functionalities.

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?

The description provides explicit guidance on when to use each action through the action list. It does not include when-not-to-use or alternatives, but the context is clear enough for an agent to select the correct action.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Can-Y/PDM_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server