Skip to main content
Glama
Sign In
PingOne Advanced Identity Cloud MCP Server

PingOne Advanced Identity Cloud MCP Server

Official
by pingidentity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set Environment Variable (ESV)

setVariable
Idempotent

Set or update an environment variable (ESV) in PingOne Advanced Identity Cloud by specifying its ID, type, and value.

Instructions

Create or update an environment variable (ESV) in PingOne AIC

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>",
      "type": "<type>"
    },
    "name": "setVariable"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesThe variable type. Determines how the value is interpreted. Note: Type cannot be changed after creation. Prefer 'array' over 'list'.
valueNoVariable value as native type (NOT JSON string). Examples: string: 'hello', array: ['a','b'], object: {"key":"val"}, bool: true, int: 42, number: 3.14, list: 'a,b,c'. The tool handles JSON serialization internally for array/object types.
variableIdYesVariable ID (format: esv-*)
descriptionNoOptional description of the variable's purpose

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / type / description
      Previous value: -"The variable type. Determines how the value is interpreted. Note: Type cannot be changed after creation. Ping recommends using 'array' instead of 'list'."New value: +"The variable type. Determines how the value is interpreted. Note: Type cannot be changed after creation. Prefer 'array' over 'list'."
    • addedInput schema / properties / variableId / minLength
      Added value: +1
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide idempotentHint=true, destructiveHint=false. Description adds no extra behavioral context beyond 'create or update', which is already implied by the annotations.

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?

The description is a single, concise sentence that directly states the tool's purpose with no unnecessary words.

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?

Given the simplicity of the tool (4 params, no output schema) and rich annotations/schema, the description is largely adequate. It could mention idempotency or type immutability, but these are covered in schema.

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 description coverage is 100%, so the schema already documents all parameter details. The tool description adds no additional meaning beyond what is in the schema.

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 verb ('Create or update') and resource ('environment variable (ESV) in PingOne AIC'), distinguishing it from siblings like deleteVariable, getVariable, etc.

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?

No explicit guidance on when to use this tool versus alternatives. The description only implies usage for setting a variable, but does not mention when not to use or provide comparisons.

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