Skip to main content
Glama

detect_vivado_environment

Detects the server-start VIVADO_PATH environment and optionally runs a bounded batch probe to verify the canonical Vivado executable identity.

Instructions

Detect the server-start VIVADO_PATH environment and optionally run a bounded batch probe; vivado_path can only assert the same canonical executable identity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
runtime_dirNo
vivado_pathNoOptional identity assertion. It must match the canonical executable identity captured from VIVADO_PATH when the MCP server started and cannot override it.
probe_launchNo
probe_timeout_sNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataYes
toolYes
messageYes
summaryYes
error_codeYes
next_stepsNo
raw_excerptNo
next_actionsNo
handoff_readyYes
stop_requiredYes
policy_allowedNo
resume_contextNo
schema_versionYes
assessment_statusYes
handoff_reviewableNo
hardware_validationNo
Behavior3/5

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

无annotations,因此描述需承担行为披露责任。它明确说明vivado_path只能断言服务器启动时捕获的同一可执行身份,不能覆盖环境,并提到probe是“bounded”,这些是有价值的行为信息。但未说明probe_launch会启动什么、是否有副作用、超时如何处理或响应形态。

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?

描述只有一句话,信息密度高,动词和核心对象前置,没有冗余词。虽然“bounded batch probe”略显含糊,但整体简洁高效。

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

Completeness2/5

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

工具有4个参数且无必填项,输出schema存在,但描述未说明runtime_dir、probe_launch、probe_timeout_s的具体作用,也未提供使用时机或边界条件。对于代理正确调用带probe的完整功能,信息不足。

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

Parameters2/5

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

schema描述覆盖率仅25%,只有vivado_path有说明,且描述为其补充了“只能断言同一身份”的约束。但runtime_dir、probe_launch、probe_timeout_s在schema和描述中都缺乏含义说明,低覆盖率下描述未能充分补偿。

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

Purpose4/5

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

描述以具体动词“Detect”和资源“server-start VIVADO_PATH environment”说明了工具功能,并提及可选的bounded batch probe。虽未直接对比兄弟工具,但环境探测用途与大多数项目/仿真/综合类工具明显区分,总体清晰。

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

描述没有说明何时应使用此工具、何时应使用替代工具,也没有提及前置条件或典型调用场景。兄弟工具中存在get_runtime_cache_status等环境相关工具,但描述未给出任何选择依据。

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/zzszzs-lll/vivado-agent-mcp'

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