Skip to main content
Glama

native_apply

Destructive

Exports a semantic circuit to a new native file with full signal wires and strict sheet bounds, preventing silent label fallback; use project_open on the returned path.

Instructions

Export the semantic circuit into a NEW native file with full signal wires and strict sheet bounds, never silent label fallback. The LED example uses authored parallel channels. Does not modify a live session. Use project_open on its returned path.

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_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds real value on top by stating that a NEW file is produced, that a live session is not modified, and that label fallback is refused rather than silent. The remaining gap is that it never says what happens if a file already exists at the target path, which is exactly where the destructive hint would bite.

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?

It is short and front-loads the core action, but the sentence about the LED example using authored parallel channels reads as incidental trivia, and phrases like 'semantic circuit' and 'strict sheet bounds' are domain jargon left unexplained.

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?

For a one-parameter tool with no output schema, the description adequately covers the return path by telling the caller to pass it to project_open. It falls short on the single parameter's meaning and on the overwrite/conflict behavior implied by destructiveHint=true.

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?

There is one parameter, 'project', with 0% schema description coverage, and the description never clarifies whether it is a name, ID, or path. Because the description does not compensate for the undocumented parameter, the baseline credit for trivially few params does not apply.

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 names a specific verb and artifact: export the semantic circuit into a NEW native file, with stated fidelity guarantees (full signal wires, strict sheet bounds). It is distinguishable in spirit from plain native_export, but it never names a sibling to contrast against, so an agent must infer the difference.

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 only implied by the word 'Export' and by the follow-up instruction to call project_open on the returned path, which at least establishes the downstream workflow. There is no explicit statement of when to pick this over native_export, native_export_led_chaser, or native_create, and no preconditions or exclusions.

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