Skip to main content
Glama

Route Environment Configuration Safely

varity_set_env
Read-onlyIdempotent

Redirects environment configuration to an approved secret-safe interface without accepting values, preventing private settings from being passed directly.

Instructions

Compatibility route for environment configuration. It never accepts values and directs private configuration to an approved secret-safe interface.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "varity_set_env"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds the meaningful point that the tool accepts no values and never stores secrets itself, but omits return behavior and whether invocation is a silent no-op.

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?

Two short sentences, front-loaded with the compatibility-route framing and followed by the security routing rule. No filler, though the second sentence would earn its place better if it named the target interface.

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 parameterless compatibility stub with rich annotations and no output schema, the definition is largely sufficient: it explains scope, the no-values constraint, and the security redirect. The remaining gap is what the caller observes after invoking it, which matters for a route that seemingly does nothing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters and an empty schema (additionalProperties=false), the baseline is 4. The description reinforces this by explicitly stating the tool 'never accepts values,' which matches the schema and prevents an agent from attempting to pass configuration inline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the domain (environment configuration) and frames the tool as a 'compatibility route,' which signals a legacy/deprecation stub rather than a functional setter. However, it never says what actually happens when the tool is invoked (no-op success, redirect, or error), so the verb is effectively missing and an agent cannot fully predict the effect.

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?

It provides one implicit when-not-to-use signal: do not pass values here, send private configuration to 'an approved secret-safe interface.' That is useful routing guidance, but the alternative interface is never named, so an agent must search the sibling list to find where to actually go.

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