Skip to main content
Glama
Sign In
Vivado MCP

Vivado MCP

by binghin2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

session_status

Retrieves status and statistics for the current Vivado session so users can inspect active project state and session health.

Instructions

Get status and statistics of the current Vivado session

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation ('Get') but does not disclose behavioral traits such as authentication needs, side effects, or what exactly 'status and statistics' include. The description is too vague to fully inform the agent.

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 a single, concise sentence with no extraneous information. Every word contributes to the purpose, and it is efficiently front-loaded.

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?

Given no output schema, no annotations, and zero parameters, the description is minimal. It is adequate for a simple status tool but lacks detail on the response format or how it differs from closely related sibling tools like 'check_session_health' or 'get_host_status'. The agent may need additional context to select this tool correctly.

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

Parameters4/5

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

The tool has zero parameters and schema coverage is 100% (empty schema). The description does not need to add parameter details, and 'status and statistics' provides minimal context. With no parameters, the baseline score of 4 is appropriate as the description adds some meaning beyond an empty 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?

The description uses a specific verb ('Get') and resource ('status and statistics of the current Vivado session'), making the tool's purpose clear. It is not a tautology and distinguishes from sibling tools like 'check_session_health' by implying broader scope, though not explicitly.

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?

No guidance on when to use this tool versus alternatives (e.g., 'check_session_health', 'get_host_status'). The description lacks when-to-use, when-not-to-use, or any contextual directives.

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