Skip to main content
Glama
the-real-talk

the-real-talk

set_variable_publishing

Hide or show a variable when publishing a library to control which variables consumers can see.

Instructions

Hide or show a variable when the library is published.

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>",
      "hidden": "<hidden>"
    },
    "name": "set_variable_publishing"
  }
}

Input Schema

NameRequiredDescriptionDefault
hiddenYes
variableIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/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 for a mutation tool, and it discloses almost nothing: not whether the flag is reversible, not whether hiding a variable breaks existing consumers of a published library, and not what permissions are required. The only behavioral fact conveyed is that the state is binary (hide/show), which the reader could already guess.

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 short sentence with no filler and the scope qualifier placed at the end where it reads naturally. It is efficient, though its brevity is as much under-specification as discipline.

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?

For a two-parameter toggle with no output schema this could be adequate, but with zero annotation and zero schema-description coverage the definition leaves an agent without the boolean polarity, the ID format, or the consequences of hiding a published variable. The core act is understandable; the operational details are not.

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%, so the description must compensate for both parameters and only partially does: 'hide or show' loosely maps to the 'hidden' boolean, but the direction (does true mean hidden?) is never stated, and 'a variable' gives no indication whether 'variableId' expects an opaque ID or a name, nor any hint about the minLength constraint.

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?

Names a specific verb pair ('Hide or show') and resource ('a variable') plus the condition ('when the library is published'), so an agent can tell this governs publication visibility rather than value, alias, or scopes. It stops short of clarifying whether the flag suppresses the variable for consumers of the published library or only in an export preview.

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 guidance, no prerequisite (e.g., must the variable live in a published library?), and no mention of alternatives among the many set_variable_* siblings. The agent must infer the trigger condition entirely from the one-line purpose.

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