Skip to main content
Glama

set_values

Assign numeric values to LSD model elements, with support for lag-specific variable settings, and save changes to config files with automatic backup.

Instructions

Set element values in a configuration, using LSD's own lsd_confgen. values maps element name to a number; every instance of the element gets the value. A variable's name sets its initial value at the first lag; "Name -2", "Name -3" ... (name, space, negative lag) set the second, third ... lag ("Name -1" is the first); a lag beyond the variable's lags, or on a parameter, is an error, and one element can appear once per call. Writes new_config.lsd, or replaces config.lsd (the old file is kept as .bak). The result says whether an existing file was replaced (replaced, backup).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYes
configYes
valuesYes
new_configNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses important side effects: writes new_config.lsd or replaces config.lsd (keeping a .bak), and the result indicates whether replacement occurred. It also states error conditions (lag beyond variable's lags, parameter lag, repeated element per call). Missing: permissions required, atomicity, or what happens on partial failure.

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?

The description is dense with useful details but somewhat disorganized; the lag-suffix explanation is verbose and interleaved with error conditions. It could be front-loaded better (e.g., start with the write behavior) but every sentence adds value.

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?

Given no annotations and no output schema, the description covers key behavioral aspects: write destination, backup behavior, return information, and error conditions. It lacks the return type details (e.g., exact fields of result) and parameter explanations for 'model', 'config', and 'new_config', but is otherwise fairly complete.

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?

With 0% schema description coverage, the description compensates well: it explains that 'values' maps element names to numbers, describes the special lag suffix syntax ('Name -2'), and notes constraints on parameter usage. However, it does not explain 'model', 'config', or 'new_config' parameters clearly (though their names are somewhat self-explanatory).

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 clearly states a specific verb+resource: setting element values in a configuration, and names the underlying mechanism (lsd_confgen). It does not explicitly differentiate from siblings like set_run_settings or edit_structure, but the resource (element values) is distinct enough.

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 by the description of how values map to elements and lags, but there is no explicit when-to-use versus alternatives, no mention of prerequisites, and no guidance on when to choose new_config vs. overwriting config.lsd.

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