Skip to main content
Glama
Sign In
Vivado MCP

Vivado MCP

by binghin2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_scopes

Lists available simulation scopes and their hierarchy, optionally returning child scopes for a specified parent to help navigate signal and breakpoint locations.

Instructions

List available scopes (hierarchy) in the simulation

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

Input Schema

NameRequiredDescriptionDefault
parentNoParent scope to list children of (default: root)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are present, so the description carries full burden. It only states the action without disclosing behavioral traits such as authentication requirements, what happens if parent is invalid, or if the list is recursive.

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 a single sentence that is concise and front-loaded with the key action. It avoids verbosity, but could optionally include more detail without becoming bloated.

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?

Given the lack of output schema, the description does not explain what the returned list contains (e.g., names, paths, metadata). The tool's role relative to sibling tools is unclear, and the simulation context is only implied.

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?

The schema description coverage is high (100% with parameter 'parent' described). The tool description adds no additional meaning beyond the schema, so baseline of 3 is appropriate.

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 clearly states the tool lists available scopes, using specific verb 'List' and resource 'scopes (hierarchy)'. However, it does not distinguish from sibling tool 'get_design_hierarchy' which may also list hierarchy but in design context.

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 is provided on when to use this tool versus alternatives like 'get_design_hierarchy' or in which scenarios. The description lacks any context about prerequisites or exclusions.

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