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 bindings, functions, and import libraries for Scripted Decision Node scripts. Essential reference for writing journey scripts in PingOne Advanced Identity Cloud.

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 handler function that executes the logic: makes an authenticated GET request to the AM realm's SCRIPTED_DECISION_NODE context endpoint and returns the bindings data.
    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 using Zod enum validator for the 'realm' parameter.
    inputSchema: {
      realm: z.enum(REALMS).describe('The realm to query')
    },
  • The tool is re-exported from the AM tools index barrel file, making it available via amTools in toolHelpers.ts.
    export { getScriptedDecisionNodeBindingsTool } from './getScriptedDecisionNodeBindings.js';
  • src/index.ts:27-43 (registration)
    Tools are registered with the MCP server via getAllTools() iteration in src/index.ts. All AM tools (including getScriptedDecisionNodeBindings) are collected by toolHelpers.ts and registered here.
    allTools.forEach((tool) => {
      const toolConfig: ToolConfig = {
        title: tool.title,
        description: tool.description
      };
    
      // Only add inputSchema if it exists (some tools like getLogSources don't have one)
      if ('inputSchema' in tool && tool.inputSchema) {
        toolConfig.inputSchema = tool.inputSchema;
      }
    
      // Add annotations if present
      if ('annotations' in tool && tool.annotations) {
        toolConfig.annotations = tool.annotations;
      }
    
      server.registerTool(tool.name, toolConfig, tool.toolFunction as any);
  • The tool is conditionally included in the allTools array (excluded in Docker mode).
      if (!isDockerMode) {
        tools.push(...(Object.values(amTools) as Tool[]));
        tools.push(...(Object.values(applicationTools) as Tool[]));
      }
    
      return tools;
    }
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to repeat that. It adds useful context by stating it shows 'what APIs and classes are available in the scripting environment', which aligns with the read-only nature. 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 sentences, front-loaded with the action and resource. No redundant or filler words. Every sentence 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?

Given the simple tool with one parameter, full schema coverage, and annotations, the description explains the return content (bindings, functions, libraries) and its relevance. It is sufficient for an agent to understand the tool's purpose and 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?

The input schema covers the single 'realm' parameter completely with an enum and description. The description does not add additional meaning to the parameter beyond what the schema 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 the tool retrieves 'available bindings (variables, functions) and allowed import libraries for Scripted Decision Node scripts.' The verb 'Retrieve' and specific resource differentiate it from sibling tools, which mostly operate on journeys, policies, or other entities.

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 explicitly notes it is 'essential reference information when writing journey scripts', providing clear context for when to use. It does not give explicit exclusions or alternatives, but the context is sufficient for a focused tool.

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