Skip to main content
Glama

create_global_variable

Creates a named global variable with an optional string default value in an RP/1 project, using the active session chain when source and output paths are omitted.

Instructions

创建具名全局变量及字符串默认值(离线结构级)。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 structure,只适用 capabilities.md 的已验样本。CLI: node create-global-variable.mjs <source.rp> <output.rp> [--default-value "Value"]

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare a non-destructive, non-open-world write, and the description adds context the annotations do not cover: offline structure-level operation, the fact that explicit paths bypass the session chain, and the restriction to validated samples in capabilities.md. It still omits failure and overwrite behavior, but that is a meaningful step beyond the annotation set.

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 purpose is front-loaded and there is no filler, but the middle sentences read as dense internal jargon (chain advancement, evidence registration) that an outside agent has to decode. The trailing CLI usage line is only relevant to a subset of callers of an MCP tool, so it does not fully earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description never says what a successful call returns or where the resulting variable is recorded, which matters for a creation tool. It compensates partially by naming the offline structure level and the source/output paths, but an agent still cannot fully predict the result.

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%, including an inline description of the session parameter, so the schema already carries the parameter burden. The description adds real meaning beyond it by mapping the CLI positional form (<source.rp> <output.rp> <VariableName> [--default-value]) onto the two mutually exclusive argument shapes. It does not explain what happens if a variable with that name already exists.

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 opens with a specific verb and resource: creating a named global variable with a string default value, scoped to offline structure level. That distinguishes it clearly from the create_* siblings (pages, projects, masters, panels). It stops short of explicitly contrasting itself against any sibling, which is why this is a 4 rather than a 5.

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?

It gives real conditional routing: in named mode, omit host source and output to use the session chain; in raw-args mode, set session:true and omit both parameters; multi-source tools still take the import source. It also notes that explicit paths do not advance the chain and that the tool only applies to validated samples in capabilities.md. What it does not do is tell you when to skip this tool in favor of another one.

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