Skip to main content
Glama

set_rules

Merge net-class and fabrication rule updates into rules.yaml in one change; invalid values are rejected with reasons, and the resulting board impact is reported.

Instructions

Change rules.yaml as ONE change, merged into it: netClasses (trackWidth, clearance, via), fabrication (profile "jlcpcb-4layer", minimums, placementRotations). A bad value is refused with the reason. The answer says what it means for the board.

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": {
      "rules": "<rules>"
    },
    "name": "set_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoCircuit to report on
rulesYese.g. { "netClasses": { "power": { "nets": ["GND"], "trackWidth": 0.5 } } }; null removes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses merge semantics ("as ONE change, merged into it"), validation behavior ("A bad value is refused with the reason"), and that the response explains board impact. It omits reversibility, permission requirements, and whether a partial merge can leave rules half-applied.

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 tight sentences, front-loaded with the action and the affected sections, with no filler. The closing sentence ("The answer says what it means for the board") is slightly vague about the actual return content, but it is short and purposeful.

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 two-parameter mutation tool with a nested free-form rules object and no output schema, the description covers what can be changed, how changes are applied, and what happens on invalid input. The main residual gap is the absence of any statement about required context or side effects on the board.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by naming the fabrication sub-fields (profile, minimums, placementRotations) and giving a concrete profile value, which the schema does not document. The `file` parameter is left to the schema.

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 ("Change rules.yaml") and enumerates the two sections it touches, netClasses and fabrication, with their sub-fields. It does not explicitly contrast itself with sibling setters like set_props or set_project, so an agent must infer the boundary, but the resource is unambiguous.

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: the description makes clear this is the tool for editing design rules, and the merge semantics hint that it is additive rather than replacing. There is no explicit when-to-use/when-not guidance, no mention of prerequisites such as a loaded circuit, and no named alternative for related edits.

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