Skip to main content
Glama
the-real-talk

the-real-talk

set_variable_code_syntax

Set a design variable’s code syntax for WEB, ANDROID, or iOS platforms so each target uses the correct value.

Instructions

Set the code syntax of a variable for WEB, ANDROID or iOS.

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": {
      "variableId": "<variableId>",
      "platform": "<platform>",
      "value": "<value>"
    },
    "name": "set_variable_code_syntax"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
platformYes
variableIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about whether this mutates existing state, whether it overwrites a previous syntax setting, what permissions or variable types are required, or whether a variable can hold syntax per platform simultaneously. Only the platform scope is conveyed, and that is already visible in the schema enum.

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 front-loaded sentence with no filler; it is efficient. The brevity borders on under-specification given the missing parameter meaning, but no sentence is wasted.

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 mutation tool with zero annotation coverage, no output schema, and no parameter documentation in the schema, the description is far too thin. An agent cannot tell what the syntax value should look like, whether the write is destructive, or what state changes result.

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% with three required parameters, so the description must compensate and does not. It never explains what the 'value' string should contain (language-specific syntax form), how 'variableId' is obtained, or that 'platform' selects which per-platform syntax entry is written.

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 names a specific verb and resource ('Set the code syntax of a variable') and states the platform scope (WEB, ANDROID, iOS), which separates it from siblings such as set_variable_value or set_variable_alias. It does not explicitly contrast itself with those siblings, but the resource is distinctive enough for an agent to identify the operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no statement of prerequisites (e.g. the variable must exist or be of a particular type), and no named alternative for related tasks. An agent gets a purpose but no routing criteria.

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