Skip to main content
Glama
moneyforward-i

Admina MCP Server

get_identity_field_configuration

Retrieve identity field configuration for an organization, including preset fields, order, metadata, and available fields. Optionally specify an identity ID to get effective configuration for a specific identity.

Instructions

Get identity field configuration of an organization. Returns preset field configurations, field order, available fields, fields metadata, and field details. Optionally pass an identityId to get the effective configuration for a specific identity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identityIdNoOptional identity ID to get the effective configuration for a specific identity

Implementation Reference

  • Handler function that executes the tool logic. Gets an AdminaApiClient, converts params to URL query params, and makes a GET API call to /identity/configuration/configuration endpoint.
    export async function getIdentityFieldConfiguration(params: GetIdentityFieldConfigurationParams) {
      const client = getClient();
      const queryParams = filtersToParams(params);
      return client.makeApiCall("/identity/configuration/configuration", queryParams);
    }
  • Zod schema defining the input: an optional identityId string to get the effective configuration for a specific identity.
    export const GetIdentityFieldConfigurationSchema = z.object({
      identityId: z
        .string()
        .optional()
        .describe("Optional identity ID to get the effective configuration for a specific identity"),
    });
  • src/index.ts:206-211 (registration)
    Tool registration in the listTools handler with name 'get_identity_field_configuration', description, and input schema.
    {
      name: "get_identity_field_configuration",
      description:
        "Get identity field configuration of an organization. Returns preset field configurations, field order, available fields, fields metadata, and field details. Optionally pass an identityId to get the effective configuration for a specific identity.",
      inputSchema: zodToJsonSchema(GetIdentityFieldConfigurationSchema),
    },
  • src/index.ts:315-316 (registration)
    Tool handler mapping routing the 'get_identity_field_configuration' tool call to the getIdentityFieldConfiguration function with schema validation.
    get_identity_field_configuration: async (input) =>
      getIdentityFieldConfiguration(GetIdentityFieldConfigurationSchema.parse(input)),
  • Helper function filtersToParams that converts a Record of filter params into URLSearchParams, filtering out undefined/null/empty values.
    export function filtersToParams(filters: Record<string, any>): URLSearchParams {
      const queryParams = new URLSearchParams();
    
      Object.entries(filters).forEach(([key, value]) => {
        if (value !== undefined && value !== null && !(Array.isArray(value) && value.length === 0)) {
          if (Array.isArray(value) && value.length > 0) {
            // Append each array value separately to generate format: key=value1&key=value2
            value.forEach((item) => {
              queryParams.append(key, String(item));
            });
          } else if (typeof value === "boolean") {
            queryParams.append(key, value.toString());
          } else {
            queryParams.append(key, String(value));
          }
        }
      });
      return queryParams;
    }
Behavior3/5

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

No annotations provided, so the description must cover behavioral traits. It correctly indicates a read operation ('Get') and describes return data, but omits side-effect statements, permissions, or rate limits. Minimal disclosure beyond obvious functionality.

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 efficient sentences: first defines purpose and outputs, second adds optional parameter usage. Front-loaded and free of fluff.

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 (one optional param, no output schema), the description is fairly complete, listing return components. Lacks details on response structure or error handling but sufficient for basic understanding.

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% for the single optional parameter. The description restates the parameter's purpose ('Optionally pass an identityId...'), adding no new semantic value beyond the schema. Baseline 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 identity field configuration and lists specific returned components (preset field configurations, field order, etc.). It distinguishes from siblings like 'get_identity_config' by focusing on field-level details.

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?

The description implies usage for obtaining field configuration but lacks explicit guidance on when to use this tool versus alternatives such as 'get_identity_config' or 'get_identity'. No when-not-to-use or alternative tool references.

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