Retrieve a specific variable's value from the active environment profile, optionally revealing secrets after confirmation. Use it to resolve environment-specific API settings during request automation.
Get the value of a specific variable from the active environment.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Variable name | |
| confirmSecret | No | Must be true when includeSecret is true | |
| includeSecret | No | Return a sensitive value instead of masking it |
Changes observed during successful MCP inspections.
v1.0.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention the secret-handling behavior (masking vs. returning sensitive values) or that confirmSecret must be true when includeSecret is true, leaving the agent to infer from the schema alone.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that front-loads the action and is free of unnecessary words. It could be slightly more informative, but it is appropriately concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple getter with no annotations or output schema, the description covers the core action but omits important context about secret handling and the relationship between includeSecret and confirmSecret. This gap makes it only partially complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage for all three parameters, so the schema already explains their meaning. The description adds only the phrase 'specific variable', which lightly reinforces the key parameter but offers no additional semantic detail beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (Get) and resource (value of a specific variable from the active environment), clearly distinguishing it from list or set operations. However, it does not explicitly name sibling tools for comparison, so a 4 is appropriate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no guidance on when to use this tool versus alternatives like env_list_variables or env_get_allowlist. It simply states the action without context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.