Skip to main content
Glama
moneyforward-i

Admina MCP Server

get_identity_custom_fields

Retrieve all custom fields configured for organizational identities, including field definitions, types (text, date, number, dropdown), and configurations.

Instructions

Get all identity custom fields configured for an organization. Returns field definitions, types (text, date, number, dropdown), and configurations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The getIdentityCustomFields async function that executes the tool logic. It calls the API endpoint '/identity/fields/custom' to retrieve all identity custom field configurations for an organization.
    export async function getIdentityCustomFields() {
      const client = getClient();
      return client.makeApiCall("/identity/fields/custom", new URLSearchParams());
    }
  • Input schema for the tool - an empty Zod object since no input parameters are needed.
    export const IdentityCustomFieldsFiltersSchema = z.object({});
  • src/index.ts:218-222 (registration)
    Tool registration in the ListToolsRequestSchema handler - defines the tool name 'get_identity_custom_fields' and its description and input schema.
    {
      name: "get_identity_custom_fields",
      description:
        "Get all identity custom fields configured for an organization. Returns field definitions, types (text, date, number, dropdown), and configurations.",
      inputSchema: zodToJsonSchema(IdentityCustomFieldsFiltersSchema),
  • src/index.ts:318-318 (registration)
    Tool handler mapping in toolHandlers map - wires 'get_identity_custom_fields' to the getIdentityCustomFields() function.
    get_identity_custom_fields: async () => getIdentityCustomFields(),
  • Imports: zod for schema validation, and getClient from the admina-api helper module.
    import { z } from "zod";
    import { getClient } from "../admina-api.js";
    
    // No input parameters needed
    export const IdentityCustomFieldsFiltersSchema = z.object({});
    
    export type IdentityCustomFieldsFilters = z.infer<typeof IdentityCustomFieldsFiltersSchema>;
    
    export async function getIdentityCustomFields() {
      const client = getClient();
      return client.makeApiCall("/identity/fields/custom", new URLSearchParams());
    }
Behavior3/5

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

With no annotations provided, the description partially fulfills the burden by indicating a non-destructive read operation and listing return content (types). However, it does not disclose potential behavioral traits such as authorization requirements, data freshness, pagination, or whether the output is sorted. The description adds value beyond a bare name but leaves room for ambiguity.

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?

A single, well-front-loaded sentence that efficiently conveys purpose, scope, and return content. No redundant or unnecessary words, making it easy for an agent to parse quickly.

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 tool's simplicity (no parameters, no output schema), the description adequately covers the core functionality: it retrieves all identity custom fields and their definitions. The mention of field types adds useful detail. It could be more precise about the exact structure of the return value, but overall it is complete enough for a straightforward get-all operation.

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?

The tool has zero parameters, and schema coverage is 100% (no parameters to document). The description correctly implies no parameters are needed. Baseline for 0 parameters is 4, and the description adds no parameter-specific info because none exists.

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 all identity custom fields for an organization, specifying the returned data (definitions, types, configurations). The verb 'Get' combined with the name unambiguously indicates a read operation, distinguishing it from sibling tools like create_identity_custom_field or delete_identity_custom_field.

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

Usage Guidelines2/5

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

The description lacks explicit guidance on when to use this tool versus alternatives. While the name implies a read-only operation, there is no mention of prerequisites, context, or when not to use it (e.g., if a specific field ID is known, another tool might be appropriate). No exclusions or comparisons are provided.

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/moneyforward-i/admina-mcp-server'

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