AgentsID Guard

Official

by AgentsID-dev

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

env_set

Sets an environment variable, requiring env.write permission to prevent unauthorized modifications by agents.

Instructions

Set an environment variable. Requires env.write permission.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Variable name
`value`	Yes	Variable value

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description correctly carries the burden of disclosing that this is a mutating operation and states the required permission (env.write). It does not mention side effects like overwriting existing variables, but the action is straightforward.

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?

Two short sentences contain all the essential information without any fluff or redundancy. Every word earns its place.

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 simple two-parameter setter with no output schema, the description is sufficient. It states the operation and the required permission. A bit more context about persistence or overwrite behavior could be added, but it is not necessary for basic usage.

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%, with name and value both described simply. The description adds no extra parameter-level detail, so the baseline of 3 is appropriate because the schema already documents both parameters.

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?

The description clearly states the tool's action with a specific verb and resource: 'Set an environment variable.' It unambiguously distinguishes this tool from the sibling reading tools env_list and env_get, and from other write tools.

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?

The description provides implied usage context (this is the setter for environment variables) but does not explicitly mention when to use it vs alternatives or any exclusions. The permission note is a prerequisite, not usage guidance.

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