Skip to main content
Glama

native_set_component

Destructive

Modify calibrated native component values, clock frequency, or program data into a new output file while requiring the source SHA-256 to verify integrity and prevent overwriting the existing output.

Instructions

Modify calibrated native component values, clock_hz or program in a NEW output file, requiring source SHA-256. No UI; never overwrites output.

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>",
      "output": "<output>",
      "ref": "<ref>",
      "properties": "<properties>",
      "expected_sha256": "<expected_sha256>"
    },
    "name": "native_set_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes
pathYes
outputYes
propertiesYes
expected_sha256Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=false, so the schema-level safety profile is known. The description adds useful facts beyond that: output goes to a NEW file, the existing output is never overwritten, and a source SHA-256 is required, but there is a mild tension with destructiveHint=true and it says nothing about error behavior or what happens to the source. With annotations carrying the safety profile, a 3 is fair.

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?

A single tight sentence with the key safety constraint (new file, no overwrite) and the SHA requirement front-loaded ahead of secondary notes. No filler, though the semicolon-delimited 'No UI' clause is somewhat cryptic.

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, non-read-only mutation tool with a nested object parameter, zero schema coverage, and no output schema, one sentence is thin. It does not explain the format or validation of expected_sha256, the meaning of ref, the structure of properties, or failure modes when the SHA does not match.

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 5 required parameters, so the description carries the burden. It obliquely covers output ('NEW output file'), expected_sha256 ('requiring source SHA-256'), and properties content ('clock_hz or program'), but 'ref' is never explained and the nested properties object's expected keys and value types remain undefined, leaving a real gap.

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 specific verb and resource: modify calibrated native component values (clock_hz or program) into a NEW output file, with a source SHA-256 requirement. It does not name or differentiate itself from close siblings such as component_set or native_apply, so an agent still has to infer which mutation tool to pick.

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?

Implies usage through constraints (requires source SHA-256, writes to a new output file, no UI, never overwrites output), which tells the agent this is a non-interactive, copy-on-write mutation. However, it never states when to choose this over component_set, native_apply, or native_read, nor any prerequisites or exclusions.

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