Skip to main content
Glama
pingidentity

PingOne Advanced Identity Cloud MCP Server

Official
by pingidentity

Get Scripted Decision Node Bindings

getScriptedDecisionNodeBindings
Read-only

Retrieve available variables, functions, and import libraries for Scripted Decision Node scripts. This reference shows the APIs and classes accessible when writing journey scripts.

Instructions

Retrieve the available bindings (variables, functions) and allowed import libraries for Scripted Decision Node scripts. This is essential reference information when writing journey scripts - it shows what APIs and classes are available in the scripting environment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
realmYesThe realm to query

Implementation Reference

  • The tool definition and handler for 'getScriptedDecisionNodeBindings'. Makes a GET request to the AM 'contexts/SCRIPTED_DECISION_NODE' endpoint for a given realm and returns the available bindings (variables, functions) and allowed import libraries for Scripted Decision Node scripts.
    export const getScriptedDecisionNodeBindingsTool = {
      name: 'getScriptedDecisionNodeBindings',
      title: 'Get Scripted Decision Node Bindings',
      description:
        'Retrieve the available bindings (variables, functions) and allowed import libraries for Scripted Decision Node scripts. This is essential reference information when writing journey scripts - it shows what APIs and classes are available in the scripting environment.',
      scopes: SCOPES,
      annotations: {
        readOnlyHint: true,
        openWorldHint: true
      },
      inputSchema: {
        realm: z.enum(REALMS).describe('The realm to query')
      },
      async toolFunction({ realm }: { realm: string }) {
        try {
          const url = buildAMRealmUrl(realm, 'contexts/SCRIPTED_DECISION_NODE');
    
          const { data, response } = await makeAuthenticatedRequest(url, SCOPES, {
            method: 'GET',
            headers: AM_SCRIPT_HEADERS_V2
          });
    
          return createToolResponse(formatSuccess(data, response));
        } catch (error: any) {
          return createToolResponse(`Failed to get scripted decision node bindings in realm "${realm}": ${error.message}`);
        }
      }
    };
  • Input schema (Zod) for the tool: requires a single 'realm' parameter that must be one of the allowed REALMS ('alpha' or 'bravo').
    inputSchema: {
      realm: z.enum(REALMS).describe('The realm to query')
  • Re-exports the getScriptedDecisionNodeBindingsTool from the AM tools index barrel file.
    export { getScriptedDecisionNodeBindingsTool } from './getScriptedDecisionNodeBindings.js';
  • URL builder helper used to construct the full URL for the contexts/SCRIPTED_DECISION_NODE endpoint.
    export function buildAMRealmUrl(realm: string, path: string): string {
      return `https://${aicBaseUrl}/am/json/${realm}/${path}`;
    }
  • API version headers (v2) used when making the request for scripted decision node bindings.
    export const AM_SCRIPT_HEADERS_V2 = {
      'accept-api-version': 'protocol=2.0,resource=1.0',
      'Content-Type': 'application/json'
    } as const;
Behavior4/5

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

Annotations already declare readOnlyHint=true (safe read) and openWorldHint=true (dynamic results). The description adds value by explaining that the tool shows available APIs and classes, which is consistent with annotations. No contradictions.

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 concise sentences with no extra words. The description front-loads the action and resource, then adds contextual value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description clearly states what the tool returns (bindings, variables, functions, import libraries) and ties it to the scripting workflow. This is sufficient given the simple input schema and clear purpose.

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% for the single parameter (realm) with an enum and description. The description does not add extra details about the parameter beyond what the schema already provides, so a baseline of 3 is appropriate.

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 it retrieves available bindings and import libraries for Scripted Decision Node scripts. It uses specific verbs ('Retrieve') and resources ('bindings, functions, import libraries'), distinguishing it from sibling get tools by its focus on scripting environment reference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description notes it is 'essential reference information when writing journey scripts', providing clear context for when to use it. However, it does not explicitly state when not to use it or mention alternatives, though given the specific purpose, the usage is fairly clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pingidentity/aic-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server