Skip to main content
Glama
pingidentity

PingOne Advanced Identity Cloud MCP Server

Official
by pingidentity

List Managed Objects

listManagedObjects
Read-only

Retrieve all managed object types available in PingOne Advanced Identity Cloud.

Instructions

Retrieve the list of all managed object types available in PingOne AIC

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main implementation of the 'listManagedObjects' tool. It defines the tool object with name, title, description, scopes, annotations, inputSchema (empty), and a toolFunction that calls the PingOne AIC API endpoint /openidm/config/managed, extracts object names from the response, and returns them as a JSON string.
    import { makeAuthenticatedRequest, createToolResponse } from '../../utils/apiHelpers.js';
    
    const aicBaseUrl = process.env.AIC_BASE_URL;
    
    const SCOPES = ['fr:idm:*'];
    
    export const listManagedObjectsTool = {
      name: 'listManagedObjects',
      title: 'List Managed Objects',
      description: 'Retrieve the list of all managed object types available in PingOne AIC',
      scopes: SCOPES,
      annotations: {
        readOnlyHint: true,
        openWorldHint: true
      },
      inputSchema: {
        // No parameters needed
      },
      async toolFunction() {
        const url = `https://${aicBaseUrl}/openidm/config/managed`;
    
        try {
          const { data } = await makeAuthenticatedRequest(url, SCOPES);
    
          const config = data as any;
    
          // Extract just the names
          const objectNames = (config.objects || []).map((obj: any) => obj.name);
    
          return createToolResponse(JSON.stringify({ managedObjectTypes: objectNames }, null, 2));
        } catch (error: any) {
          return createToolResponse(`Error listing managed objects: ${error.message}`);
        }
      }
    };
  • Input schema for listManagedObjects — empty object since no parameters are needed.
    inputSchema: {
      // No parameters needed
    },
  • src/index.ts:27-44 (registration)
    The tool registration loop in src/index.ts. All tools (including listManagedObjects) are registered with the MCP server via server.registerTool(tool.name, toolConfig, tool.toolFunction).
    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);
    });
  • getAllTools() collects listManagedObjectsTool (via managedObjectTools namespace) and all other tools, which are then registered in src/index.ts.
    export function getAllTools(): Tool[] {
      const isDockerMode = process.env.DOCKER_CONTAINER === 'true';
    
      const tools: Tool[] = [
        ...(Object.values(managedObjectTools) as Tool[]),
        ...(Object.values(logTools) as Tool[]),
        ...(Object.values(themeTools) as Tool[]),
        ...(Object.values(esvTools) as Tool[]),
        ...(Object.values(featureManagementTools) as Tool[])
      ];
    
      // Only include AM tools in non-Docker mode (requires browser-based PKCE auth)
      if (!isDockerMode) {
        tools.push(...(Object.values(amTools) as Tool[]));
        tools.push(...(Object.values(applicationTools) as Tool[]));
      }
    
      return tools;
    }
  • makeAuthenticatedRequest utility used by the handler to make authenticated API calls to PingOne AIC.
    export async function makeAuthenticatedRequest(
      url: string,
      scopes: string[],
      options: RequestInit = {}
    ): Promise<{ data: unknown; response: Response }> {
      const token = await getAuthService().getToken(scopes);
    
      const response = await fetch(url, {
        ...options,
        headers: {
          Authorization: `Bearer ${token}`,
          'User-Agent': USER_AGENT,
          // Only add Content-Type header if the request has a body
          ...(options.body && { 'Content-Type': 'application/json' }),
          ...options.headers
        }
      });
    
      if (!response.ok) {
        const errorBody = await response.text();
        throw new Error(formatError(response, errorBody));
      }
    
      // Handle empty responses (e.g., 204 No Content or DELETE operations)
      const contentLength = response.headers.get('content-length');
      const data = response.status === 204 || contentLength === '0' ? null : await response.json();
    
      return { data, response };
    }
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds context that it retrieves object types (not instances), providing additional clarity beyond 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?

Single sentence, front-loaded with key information. No unnecessary words.

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

Completeness3/5

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

Description is adequate for a simple list operation, but does not specify the return format or structure. Could be clearer about what the output contains (e.g., names, ids).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters, and schema coverage is 100%. With 0 parameters, baseline is 4. Description does not add parameter details, but none are needed.

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?

Clearly specifies verb 'Retrieve', resource 'list of all managed object types', and context 'PingOne AIC'. Distinguishes from sibling tools like queryManagedObjects.

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 when or when-not guidelines or alternatives mentioned. However, the purpose is straightforward and easily inferred from name and description.

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