Skip to main content
Glama
Hachimeder

maxplus2-mcp

by Hachimeder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Parse design and waveform files directly

project_parse_file
Read-onlyIdempotent

Parse MAX+plus II project files (GDF, SCF, ACF, TBL, EDIF, reports) into structured records, events, traces, and connections. Returns original path, bytes, SHA-256, and limits.

Instructions

File-first structured parsing of strict GDF text/geometry, SCF scalar/bus logic events in ns, ACF assignments, TBL traces, reports and EDIF connections. Returns original path/bytes/SHA-256 and explicit limitations. Use gdf_geometry for paginated symbol definitions/placements and netlist_export for GDF circuit connections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
netNoOptional exact EDIF net identifier/name to inspect its connections.
cellNoOptional EDIF library/cell identifier for inspecting a hierarchical cell; defaults to the top design.
pathYesSource file relative to the project/workspace; absolute paths must remain within that scope.
limitNoMaximum text records/trace rows/diagnostics or SCF events per signal; default 100, SCF defaults to 20 and may reduce to fit the result budget.
formatNoDefault auto detects the file extension; explicit formats still validate their content.
offsetNoZero-based item/event page offset, default 0.
signalNoOptional exact SCF signal or display bus name.
endTimeNoSCF time-range end in ns; default entire duration.
projectNoExisting ACF project to scope file paths to its directory.
startTimeNoSCF time-range start in ns, default 0.
workspaceNoWorkspace scope when project is omitted; defaults to MAXPLUS2_WORKSPACE.
signalLimitNoMaximum SCF signals per page; default 5. Use nextSignalOffset to continue.
signalOffsetNoZero-based SCF signal page offset; default 0.
endpointLimitNoMaximum endpoints per EDIF net, default 20; use nextEndpointOffset to continue.
endpointOffsetNoZero-based endpoint offset within each EDIF net.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that: it discloses the returned artifacts (original path, bytes, SHA-256) and the presence of 'explicit limitations', which is meaningful output behavior given no output schema exists.

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?

Three sentences: what it parses, what it returns, and which siblings to prefer instead. Front-loaded with the highest-value information and no filler or restatement of the title.

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 15-parameter multi-format parser with no output schema, the description covers formats, return metadata, limitations, and sibling alternatives. It does not map which parameters apply to which format, but the 100%-covered schema carries that burden, so nothing critical is missing.

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% across all 15 parameters, so the schema already documents pagination limits, time ranges, and format enum semantics in detail. The description adds only the passing hint of 'events in ns' and the paginated-symbols reference; with the schema doing the heavy lifting, baseline 3 is correct.

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?

States a specific verb (parsing) and enumerates the exact resource classes it handles: GDF text/geometry, SCF logic events, ACF assignments, TBL traces, reports and EDIF connections. It also names sibling tools (gdf_geometry, netlist_export) and the cases they own, so an agent can separate this general parser from format-specific tools without opening schemas.

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 routes two cases to alternatives ('Use gdf_geometry for paginated symbol definitions/placements and netlist_export for GDF circuit connections'), which is strong when-not guidance. It never states the positive trigger condition in so many words, so the 'when to use this' half is implied rather than spelled out.

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