Skip to main content
Glama
moneyforward-i

Admina MCP Server

get_identity_config

Retrieve effective configuration for identity fields of a specific identity by providing its identityId.

Instructions

Get configuration for identity fields of a specific identity. Required to filter by a specific identityId to see the effective configuration for that identity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identityIdYes

Implementation Reference

  • The actual handler function that executes the tool logic. It gets the API client, extracts identityId from filters, constructs query params from remaining fields, and makes an API call to /identity/configuration/configuration/{identityId}.
    export async function getIdentityConfig(filters: IdentityConfigFilters) {
      const client = getClient();
      const { identityId, ...rest } = filters;
      const queryParams = filtersToParams(rest);
      return client.makeApiCall(`/identity/configuration/configuration/${identityId}`, queryParams);
    }
  • Zod schema defining the input: an object with a required identityId string field.
    export const IdentityConfigFiltersSchema = z.object({
      identityId: z.string(),
    });
  • src/index.ts:212-217 (registration)
    Tool registration in the ListToolsRequestSchema handler: defines the tool name 'get_identity_config', its description, and input schema.
    {
      name: "get_identity_config",
      description:
        "Get configuration for identity fields of a specific identity. Required to filter by a specific identityId to see the effective configuration for that identity.",
      inputSchema: zodToJsonSchema(IdentityConfigFiltersSchema),
    },
  • src/index.ts:317-317 (registration)
    Tool handler registration in the toolHandlers map: maps the name 'get_identity_config' to an async function that parses input with IdentityConfigFiltersSchema and calls getIdentityConfig.
    get_identity_config: async (input) => getIdentityConfig(IdentityConfigFiltersSchema.parse(input)),
  • Re-export of getIdentityConfig module from the tools barrel index file.
    export * from "./getIdentityConfig.js";
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the purpose without mentioning permissions, side effects, or whether it is read-only, which is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two short sentences, no redundant information. However, it could be slightly more structured to improve readability.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It does not describe the return format, example output, or how this relates to sibling tools like get_identity_field_configuration.

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

Parameters2/5

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

The only parameter (identityId) lacks schema description. The description adds minimal value by saying 'filter by a specific identityId' but does not explain what identityId represents or how to use it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it gets configuration for identity fields for a specific identity, using a specific verb and resource. However, it does not differentiate from siblings like get_identity_field_configuration.

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 indicates that an identityId is required to see the effective configuration, implying usage context. But it does not provide when to use this tool versus alternatives or exclude misuse cases.

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