Skip to main content
Glama

add_variables

Add multiple stocks, auxiliaries, flows, connectors, and modules to an existing model in a single all-or-nothing call. On error, the model remains unchanged and the failing item is identified.

Instructions

Add multiple stocks, auxiliaries, flows, connectors, and/or modules to an existing model in one call. All-or-nothing — on any item error the model is left unchanged and the error names the failing item (stage + index).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
model_idNoSession-scoped model ID. Optional; defaults to the current model for this session.
stocksNoStocks to add (applied first)
auxsNoAuxiliary variables to add (applied after stocks)
flowsNoFlows to add (applied after stocks and auxs)
connectorsNoExplicit connectors to add (applied after variables)
modulesNoModules to create (applied last)
sync_connectorsNoRun sync_connectors_from_equations after applying items
validateNoInclude validation results in the response
Behavior4/5

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

The description discloses atomic 'all-or-nothing' behavior and error naming, which are valuable beyond annotations (which only indicate non-read-only, non-destructive).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with purpose, and includes a key behavioral note with no wasted words.

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 the complexity (8 parameters, nested objects) and sibling tools, the description adequately covers core functionality and atomicity; the schema complements details.

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

Parameters3/5

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

Schema coverage is 100%, and the description adds no parameter details beyond what the schema already provides, resulting in a baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool adds multiple types of items (stocks, auxiliaries, flows, connectors, modules) to an existing model in one call, distinguishing it from sibling tools that add single item types.

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?

The description implies batch usage but does not explicitly guide when to use this tool versus individual add tools, lacking criteria or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bradleylab/stella-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server