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

estimate

Estimate FPGA power consumption quickly, get part recommendations based on budget and resources, or list supported FPGA families.

Instructions

快速功耗估算 / Part 推荐 / 系列列表——无需 PDM 会话。

action 决定操作:

  • "quick": 快速功耗估算,基于 XPE 公开系数 + 线性模型,秒级返回。精度约 ±40%。

  • "recommend": 根据功耗预算和资源需求推荐合适的 Part 型号。

  • "families": 列出支持快速估算的 FPGA 系列及典型参数。

quick 参数: part: FPGA 器件型号,如 "xc7a100tcsg324-1"。 clock_mhz: 主时钟频率 (MHz)。 lut_pct: LUT 利用率百分比 (0-100)。 ff_pct: FF 利用率百分比 (0-100)。 bram_pct: BRAM 利用率百分比 (0-100)。 dsp_pct: DSP 利用率百分比 (0-100)。 io_count: IO 引脚数量。 io_standard: IO 标准,如 "LVCMOS33"、"LVDS"、"SSTL15"。 io_toggle: IO 翻转率百分比 (0-100),默认 12.5。 gt_count: GT 高速收发器数量。 gt_rate: GT 线速率 (Gbps)。 temp: 环境温度 (°C),默认 25。 airflow: 风流量 (LFM),默认 250。 heatsink: 散热器类型 (none/small/medium/large),默认 medium。

recommend 参数: budget: 总功耗预算 (W)。 logic_cells: 需要的逻辑单元数。 bram_kb: 需要的 BRAM (Kb)。 dsp_slices: 需要的 DSP Slice 数。 io_count: 需要的 IO 引脚数。 gt_count: 需要的 GT 收发器数。 family: 限定系列,如 "7series"、"ultrascale"。 max_count: 最多返回结果数,默认 5。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
partNo
tempNo
actionYes
budgetNo
familyNo
ff_pctNo
airflowNo
bram_kbNo
dsp_pctNo
gt_rateNo
lut_pctNo
bram_pctNo
gt_countNo
heatsinkNomedium
io_countNo
clock_mhzNo
io_toggleNo
max_countNo
dsp_slicesNo
io_standardNoLVCMOS33
logic_cellsNo

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 bears full responsibility. It discloses that quick estimation is based on a linear model, returns in seconds, and has ±40% accuracy. It also provides default values for parameters. However, it does not mention error conditions, idempotency, or permission requirements.

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 summary line, action sections, and parameter lists. It is front-loaded with the main purpose. However, it is lengthy due to detailed parameter explanations; some default values are redundant with the schema, but overall efficient.

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 complexity of the tool (21 parameters, three modes) and the presence of an output schema, the description is fairly complete. It covers all actions and parameters, though it could mention how the output varies by action or handle error scenarios.

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?

The schema description coverage is 0%, yet the description comprehensively explains every parameter for 'quick' and 'recommend' actions, including units, defaults, and value ranges (e.g., lut_pct 0-100). This fully compensates for the lack of schema descriptions.

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 the tool does three distinct operations: quick power estimation, part recommendation, and listing families. It uses specific verbs and resource targets, and although it doesn't explicitly differentiate from siblings, the action-based design implies distinct use cases.

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 clear context for each action, such as when to use 'quick' (rough estimation) vs 'recommend' (part selection). However, it lacks explicit guidance on when not to use this tool or alternatives among sibling tools like 'power' or 'explore'.

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