Skip to main content
Glama
the-real-talk

the-real-talk

create_variable

Creates a COLOR, FLOAT, STRING, or BOOLEAN variable in an existing collection with a value for each mode and returns its ID.

Instructions

Create a variable (COLOR, FLOAT, STRING or BOOLEAN) in an existing collection, with a value for each mode. Colors are #RRGGBB(AA) or {r,g,b,a} in 0-1. Returns the variable ID.

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": {
      "collectionId": "<collectionId>",
      "name": "<name>",
      "type": "<type>",
      "values": "<values>"
    },
    "name": "create_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesVariable name (use / for groups)
typeYesCOLOR = color, FLOAT = number, STRING = text, BOOLEAN = boolean
valuesYesValue per mode, keyed by mode name or mode ID
collectionIdYesID of the collection

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a mutation semantics, the accepted color encodings, and that it returns the variable ID, but it is silent on error behavior (duplicate names, unknown collectionId or mode key), permissions, and whether all modes must be covered or only some.

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?

Two compact sentences with the action, the type set, the placement constraint, the value/color format, and the return value front-loaded. No filler or redundant phrasing.

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 simple four-parameter creation tool with a fully described schema, the description covers purpose, value format, and the return value (compensating for the absent output schema). The main residual gap is failure/validation behavior, which matters for a write tool with no annotations.

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 description coverage is 100%, so all four parameters are already documented, including the per-mode values map and the color pattern. The description's color format note largely restates the schema's regex and object shape, and "a value for each mode" echoes the schema's own wording, so little new meaning is added beyond structured data.

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 gives a specific verb and resource ("Create a variable") plus the supported type enumeration and where the result lands ("in an existing collection"), which implicitly separates it from create_variable_collection. It never names a sibling outright, so the differentiation is inferred rather than stated.

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 agent can infer this is the tool for making a new variable once a collection exists, but there is no explicit when-to-use or when-not guidance and no pointer to alternatives such as create_variable_collection or set_variable_alias. No prerequisites (collection must already exist, modes must already be defined) are spelled out beyond the phrase "existing collection".

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

Deploy Server

Other Tools