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

scenario

Manage FPGA power estimation scenarios: adjust environment, clock frequency, toggle rate, resource utilization, recalculate power, and compare snapshots.

Instructions

统一的场景管理入口——通过 action 参数选择操作。

Actions:

  • "set_environment" — 设置环境参数(温度、风流量、散热器)。 需要 temp,可选 airflow(默认 250)、heatsink(默认 medium)。

  • "set_clock_frequency" — 修改某个时钟的频率。 需要 namefreq_mhz

  • "set_toggle_rate" — 修改某个 Block 的信号翻转率。 需要 blockpct(0–100)。

  • "set_resource_util" — 修改某个 Block 的资源用量(绝对数量)。 需要 block,可选 lut / ff / bram / dsp (-1 表示不修改对应项)。填入实际使用的资源数, 如 lut=50000 表示已用 50000 个 LUT。

  • "recalculate" — 参数修改后重新计算功耗。

  • "compare" — 对比最近两次功耗快照(依赖 power(action="summary") 保存的快照),

    10% 差异标记 WARN。

Args: action: 操作类型(见上)。 session_id: 目标会话 ID。 temp: 环境温度 (°C)(set_environment)。 airflow: 风流量 LFM(set_environment,默认 250)。 heatsink: 散热器类型 none/small/medium/large(set_environment,默认 medium)。 name: 时钟名称(set_clock_frequency)。 freq_mhz: 新频率 MHz(set_clock_frequency)。 block: Block 名称(set_toggle_rate / set_resource_util)。 pct: 翻转率百分比 0–100(set_toggle_rate)。 lut: 已用 LUT 数量(set_resource_util, -1 跳过)。 ff: 已用 FF 数量(set_resource_util, -1 跳过)。 bram: 已用 BRAM Tile 数量(set_resource_util, -1 跳过)。 dsp: 已用 DSP Slice 数量(set_resource_util, -1 跳过)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ffNo
dspNo
lutNo
pctNo
bramNo
nameNo
tempNo
blockNo
actionYes
airflowNo
freq_mhzNo
heatsinkNo
session_idNodefault

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description discloses behavioral traits like the need to call recalculate after modifications and the dependency on power(action='summary') for compare. No annotations are provided, so the description carries full burden. It lacks details on side effects, reversibility, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear opening, bulleted actions, and parameter lists. Every sentence serves a purpose, and it is concise given the complexity of 6 actions and 13 parameters.

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 multi-action tool with conditional parameters, the description covers all actions' inputs and notes cross-dependencies (e.g., compare requires power snapshots). It omits output schema details but that is acceptable given output schema exists. Slight miss on not describing return structure for recalculate or set operations.

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 coverage, the description fully compensates by explaining each parameter's purpose, constraints (e.g., pct 0-100, lut default -1), and per-action grouping. This adds significant meaning beyond the raw schema.

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 defines the tool as a unified scenario management entry point with specific actions, each described with verb and resource. It distinguishes from sibling tools like power, estimate, and session by focusing on scenario parameter manipulation.

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 explicitly lists each action and its required/optional parameters, guiding the agent on when to use each. However, it does not provide exclusions or contrast with sibling tools for when not to use this tool.

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