Skip to main content
Glama
Sign In
Kurlo

Kurlo

by stormhop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Set an environment variable

set_variable

Set a non-secret environment variable, creating the environment if it does not exist, and write it to the Git-shared file so requests can reuse it as {{key}}.

Instructions

Set a non-secret variable in an environment, creating the environment if it does not exist. The value is written to the environment's file, so it is shared through Git; never use it for a secret. Secret variables and protected environments can only be changed in Kurlo.

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": {
      "key": "<key>",
      "value": "<value>"
    },
    "name": "set_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesVariable name, used in requests as {{key}}.
valueYesValue.
workspaceNoWorkspace name, when the folder holds more than one.
descriptionNoWhat the variable is for.
environmentNoEnvironment name. Defaults to the one the server was started with.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.1

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that the value is persisted to the environment's file and shared through Git, and that a missing environment is created as a side effect. It does not say what happens when the key already exists (overwrite vs error), which matters given idempotentHint=false.

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?

Three tight sentences: capability, persistence/Git implication, then the security boundary. Front-loaded with the action and scoping constraint, with no filler.

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?

With no output schema and full schema coverage, the description supplies the missing behavioral context: Git persistence, non-secret constraint, and environment auto-creation. Only the overwrite behavior for an existing key is left unexplained.

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 five parameters are already documented, including the environment default and workspace disambiguation. The description adds no additional parameter meaning, so the baseline 3 applies.

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?

States a specific verb and resource (set a non-secret variable in an environment) and immediately scopes it away from secrets and protected environments. An agent can distinguish this from list_environments or save_request without reading the schema.

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

Usage Guidelines4/5

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

Explicitly names the negative case: 'never use it for a secret' and directs secret/protected changes to Kurlo. It also documents the side effect of creating a missing environment. What's missing is a positive routing rule toward a sibling tool (e.g., when to prefer list_environments first), but the exclusions are strong.

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