Skip to main content
Glama
Sign In
Vivado MCP

Vivado MCP

by binghin2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

check_session_health

Checks whether a Vivado session is responsive and automatically restarts it when commands time out or behave unexpectedly.

Instructions

Check if Vivado session is responsive and recover if needed. Use this if commands are timing out or behaving unexpectedly.

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": "check_session_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
auto_recoverNoRestart session if unhealthy (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses the potential side effect of restarting the session via auto_recover, but lacks detail on the exact recovery process and failure behavior.

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, front-loaded with purpose, no unnecessary words. Every sentence is informative.

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 simple health-check tool with one parameter and no output schema, the description adequately covers purpose, usage, and side effects. Missing return value details are acceptable given no output schema.

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 description coverage is 100% for the single parameter, and the description adds minimal value beyond that (only mentions recovery generically). Baseline 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?

The description clearly states the tool checks Vivado session responsiveness and can recover it, which distinguishes it from sibling tools like 'get_host_status' and 'session_status'.

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?

Provides clear guidance to use the tool when commands are timing out or behaving unexpectedly, but does not mention when not to use it or alternative tools.

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