Skip to main content
Glama

native_export_led_chaser

Destructive

Generates native .pdsprj, C51 source, and HEX files from the example_led_chaser topology using explicit wires and named nets; verify each export at runtime.

Instructions

Generate a native .pdsprj, C51 source and HEX from the exact example_led_chaser topology. Calibrated explicit wires and named nets. Each export still needs its own runtime verification.

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": {
      "project": "<project>"
    },
    "name": "native_export_led_chaser"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and openWorldHint=false, and the description adds genuinely useful context: it emits multiple file artifacts and that a successful export is not proof of correctness ('needs its own runtime verification'). It still omits where files land, whether existing files are overwritten, and what the destructive aspect actually applies to, which is the main behavioral gap for a write tool.

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?

Three short sentences, front-loaded with the concrete output artifacts. No filler, though the middle fragment 'Calibrated explicit wires and named nets' is vague enough to border on noise.

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?

Because there is no output schema, naming the three produced artifacts is the right compensation and it is present. However, for a destructive multi-file writer with an undocumented parameter, missing output locations, overwrite semantics, and prerequisites leave the picture incomplete.

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 coverage is 0% with a single required 'project' string, so the description carries the full burden. It only implies the export is bound to the example_led_chaser topology and never explains whether 'project' is a name, path, or identifier, nor how it interacts with that fixed topology.

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?

States a concrete verb ('Generate') and enumerates the exact artifacts produced: a native .pdsprj, C51 source, and HEX. Scoping it to 'the exact example_led_chaser topology' separates it from the generic native_export and export_netlist siblings, so an agent can tell which variant it wants without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the tool is for producing deliverables from the led-chaser example, and the sentence about runtime verification hints at its role in a build-then-check flow. There is no explicit when-not clause and no alternative named, so the agent must infer that export_netlist/export_svg cover other artifact types.

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