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

clock

Manage clocks and clock managers: list, create, delete, edit, and replace clocks or configure clock managers with settings like frequency, IO type, and VCO range.

Instructions

统一时钟管理工具 — 通过 action 参数选择操作。

Clock 操作: list — 列出所有时钟 create — 创建时钟 (name, freq, io_type, io_standard, is_gated, min_freq) delete — 删除时钟 (name) edit — 编辑时钟 (name, freq, io_type, io_standard, is_gated, min_freq) settings — 获取时钟设置 (name) sample_settings — 获取时钟示例设置模板 replace — 替换时钟 (name, other, blocks)

Clock Manager 操作: mgr_types — 列出可用时钟管理器类型 mgr_list — 列出所有时钟管理器 mgr_create — 创建时钟管理器 (name, type, input_clock, vco_range) mgr_delete — 删除时钟管理器 (name) mgr_settings — 获取时钟管理器设置 (name)

Args: action: 操作类型,见上。 name: 时钟/管理器名称。 freq: 时钟频率 (MHz)。 io_type: IO 类型,如 "HD"、"HP"。 io_standard: IO 标准,如 "LVCMOS 1.8V"、"LVDS"。 is_gated: 是否为门控时钟 (create: bool; edit: "true"/"false"/"")。 min_freq: 最低缩放频率 (MHz),0 表示无。 other: replace 时的目标时钟名称。 blocks: replace 时限定作用的 Block 列表,逗号分隔。 type: 管理器类型,如 "MMCM"、"DPLL"、"XPLL"。 input_clock: 管理器输入时钟名称。 vco_range: VCO 范围,"Low" 或 "High"。 session_id: 目标会话 ID。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
freqNo
nameNo
typeNo
otherNo
actionYes
blocksNo
io_typeNo
is_gatedNo
min_freqNo
vco_rangeNoLow
session_idNodefault
input_clockNo
io_standardNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the operations and parameters but does not mention side effects, authorization needs, rate limits, or behavioral traits beyond the listed actions.

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 clear sections for clock and clock manager operations, and front-loads the purpose. It is slightly verbose but organized for readability.

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?

Given the high complexity (13 parameters, many actions) and presence of an output schema, the description is fairly complete. It covers all actions and parameters, though it lacks explanation of default values, error handling, or operation ordering.

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?

With schema description coverage at 0%, the description compensates by explaining each parameter in the context of actions (e.g., 'freq: 时钟频率 (MHz)'). This adds significant meaning beyond schema titles. However, some parameters like 'session_id' are only listed in the args section without per-action context.

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 identifies the tool as a unified clock management tool ('统一时钟管理工具') and enumerates all specific operations (list, create, delete, edit, etc.) for both clocks and clock managers. This distinguishes it from siblings like 'session' or 'power_design'.

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 lists actions and their parameters, implying usage for clock management tasks. However, it lacks explicit guidance on when to use this tool versus alternatives, and does not provide exclusion criteria or prerequisites.

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