Skip to main content
Glama
Sign In
Vivado MCP

Vivado MCP

by binghin2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

start_session

Starts a persistent Vivado TCL session for subsequent commands; call it first to enable conversational FPGA design flows.

Instructions

Start a persistent Vivado TCL session. Must be called before other commands.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
vivado_pathNoPath to Vivado executable (default: 'vivado' from PATH)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so the description must carry the burden. It states the core behavior but doesn't disclose details like whether it returns a session handle, any side effects, or prerequisites beyond path. Minimal but not misleading.

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?

Two sentences with no wasted words. The essential information is front-loaded and every word earns its place.

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

Completeness3/5

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

With one optional parameter, no output schema, and a simple purpose, the description is adequate but incomplete. It doesn't explain what the tool returns or if it can be called multiple times. More context would benefit the agent.

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

Parameters3/5

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

Schema has 100% description coverage for the single parameter (vivado_path). The description adds no extra meaning beyond the schema's own description. Baseline of 3 is appropriate.

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?

Description clearly states the verb 'Start' and the resource 'persistent Vivado TCL session'. It also provides the essential context that it must be called before other commands, which distinguishes it from sibling tools that depend on an active session.

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?

Explicitly says 'Must be called before other commands', which gives clear guidance on when to use this tool. Could be improved by noting when not to use it (e.g., if a session already exists), but the statement is functional.

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

Deploy Server

Other Tools