Skip to main content
Glama
moneyforward-i

Admina MCP Server

get_identities_stats

Retrieve organization identity statistics to analyze management type counts, HR master integration, and domain lists for identity distribution insights.

Instructions

Get identities statistics for an organization. Returns management type counts, HR master integration information, and domain lists. Use this to understand the distribution of identities across different management types and HR systems.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler function 'getIdentitiesStats' that calls the API at '/identity/stats' to get identity statistics for an organization.
    import { z } from "zod";
    import { getClient } from "../admina-api.js";
    
    export const GetIdentitiesStatsSchema = z.object({});
    
    export type GetIdentitiesStatsParams = z.infer<typeof GetIdentitiesStatsSchema>;
    
    export async function getIdentitiesStats(_params: GetIdentitiesStatsParams) {
      const client = getClient();
      return client.makeApiCall("/identity/stats", new URLSearchParams());
    }
  • Input schema 'GetIdentitiesStatsSchema' - an empty Zod object (no parameters required).
    export const GetIdentitiesStatsSchema = z.object({});
  • Type definition 'GetIdentitiesStatsParams' inferred from the schema.
    export type GetIdentitiesStatsParams = z.infer<typeof GetIdentitiesStatsSchema>;
  • src/index.ts:231-235 (registration)
    Registration of the 'get_identities_stats' tool with description and input schema.
      name: "get_identities_stats",
      description:
        "Get identities statistics for an organization. Returns management type counts, HR master integration information, and domain lists. Use this to understand the distribution of identities across different management types and HR systems.",
      inputSchema: zodToJsonSchema(GetIdentitiesStatsSchema),
    },
  • src/index.ts:321-321 (registration)
    Handler binding: maps the tool name 'get_identities_stats' to the actual function call with schema parsing.
    get_identities_stats: async (input) => getIdentitiesStats(GetIdentitiesStatsSchema.parse(input)),
Behavior2/5

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

No annotations provided, so description must carry full burden. Mentions it returns organizational stats but does not indicate if it is read-only, requires specific permissions, or any side effects.

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 purpose and examples, no wasted words.

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?

No output schema exists, but description covers key return elements (management type counts, HR info, domain lists). Could be more precise about structure, but adequate.

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?

Input schema has zero parameters, so baseline is 4. Description adds value by detailing the returned data, which is sufficient.

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 states 'Get identities statistics for an organization' and lists specific outputs (management type counts, HR integration info, domain lists). Distinguishes from sibling tools like get_identities which return identity 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?

Suggests using it to understand distribution of identities across management types and HR systems, but does not explicitly exclude cases or mention alternatives among siblings.

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