Skip to main content
Glama

native_verify

Destructive

Automates circuit and cache verification by opening and comparing designs, running simulations, checking active-low cyclic net order, backing up files, and reporting crash evidence.

Instructions

Autonomously open, save, close, reopen, compare circuit/cache, run and sample, pause/resume/stop, close and collect crash evidence. Net order is checked for calibrated active-low cyclic output. Creates file backups and reports.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "native_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
netsNo
pathYes
secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description meaningfully adds to that: it discloses that the tool creates file backups, may produce crash evidence, and mutates the circuit file through open/save/close cycles. This tells the agent the operation is risky but recoverable. It stops short of stating exactly which files are overwritten or what the report contains, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences pack a lot of information, but they read as an unstructured activity log ('close, reopen ... close and collect') with a duplicated 'close' and no hierarchy between primary behavior and side effects. Front-loading the core purpose before the sub-steps would improve it.

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?

For a destructive, multi-step verification tool with three undocumented parameters and no output schema, the description should explain parameter roles and what the report contains. It covers internal behavior reasonably but leaves the agent unable to construct a valid call confidently or anticipate the returned evidence.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must compensate and largely does not. 'Net order is checked' faintly hints at the nets array and 'run and sample' hints at the seconds duration, but neither the expected net name format, the 2-64/3-25 bounds, nor what 'path' points to (project file? circuit file?) is clarified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name and description imply a verification workflow (open/save/reopen, compare circuit vs cache, run and sample, check net order for calibrated active-low cyclic output). But the description is a comma-spliced list of sub-steps rather than a single statement of what the tool verifies and what a pass/fail means. It does not distinguish itself from sibling 'native_check' or 'native_inspect', leaving the agent to guess which verification entry point to use.

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?

There is no when-to-use guidance, no prerequisites (e.g. project must be built/flashed), and no mention of alternatives. The agent is told what happens internally but never told under what conditions it should pick this over native_check, native_inspect, or native_export.

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