Skip to main content
Glama
moneyforward-i

Admina MCP Server

get_service_accounts

Retrieve accounts for a specific service using its serviceId. Filter by keyword, roles, status, and more to find user accounts.

Instructions

Return a list of accounts for a specific service. The serviceId can be obtained from the get_services tool. Can be searched by email/name of the account by keyword

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceIdYes
limitNo
cursorNo
keywordNo
sortByNo
sortOrderNo
workspaceIdsNo
twoFaNo
rolesNo
serviceRolesNo
typesNo
employeeTypesNo
employeeStatusesNo
statusesNo
includeDeletedNo
expandIdentitiesNo
onlyInactiveNo
licensesNo
alertTypeNo
alertStatusNo

Implementation Reference

  • The asynchronous handler function that executes the 'get_service_accounts' tool logic. It extracts the serviceId, converts remaining filters to query parameters, and makes an API call to /services/{serviceId}/accounts.
    export async function getServiceAccounts(filters: ServiceAccountFilters) {
      const client = getClient();
      const { serviceId, ...rest } = filters;
      const queryParams = filtersToParams(rest);
    
      return client.makeApiCall(`/services/${serviceId}/accounts`, queryParams);
    }
  • Zod schema for input validation of get_service_accounts. Defines all filter parameters including serviceId (required), limit, cursor, keyword, sortBy, sortOrder, workspaceIds, twoFa, roles, serviceRoles, types, employeeTypes, employeeStatuses, statuses, includeDeleted, expandIdentities, onlyInactive, licenses, alertType, and alertStatus.
    export const ServiceAccountFiltersSchema = z.object({
      serviceId: z.number(),
      limit: z.number().optional(),
      cursor: z.string().optional(),
      keyword: z.string().optional(),
      sortBy: z.string().optional(),
      sortOrder: z.string().optional(),
      workspaceIds: z.array(z.number()).optional(),
      twoFa: z.boolean().optional(),
      roles: z
        .array(z.enum(["admin", "guest", "other"]))
        .length(1, "roles must be an array with exactly one element")
        .optional(),
      serviceRoles: z.array(z.string()).optional(),
      types: z.array(z.enum(["employee", "guest", "system", "unknown"])).optional(),
      employeeTypes: z
        .array(
          z.enum([
            "board_member",
            "full_time_employee",
            "fixed_time_employee",
            "temporary_employee",
            "part_time_employee",
            "secondment_employee",
            "contract_employee",
            "collaborator",
            "group_address",
            "shared_address",
            "test_address",
            "other",
            "unknown",
            "unregistered",
          ]),
        )
        .length(1, "employeeTypes must be an array with exactly one element")
        .optional(),
      employeeStatuses: z
        .array(z.enum(["active", "on_leave", "draft", "preactive", "retired", "untracked"]))
        .length(1, "employeeStatuses must be an array with exactly one element")
        .optional(),
      statuses: z
        .array(z.enum(["active", "on_leave", "draft", "preactive", "retired", "untracked"]))
        .length(1, "employeeStatuses must be an array with exactly one element")
        .optional(),
      includeDeleted: z.boolean().optional(),
      expandIdentities: z.boolean().optional(),
      onlyInactive: z.boolean().optional(),
      licenses: z.array(z.string()).optional(),
      alertType: z
        .enum(["retired_account", "inactive_account", "on_leave_account", "unknown_account", "public_files"])
        .optional(),
      alertStatus: z.enum(["muted", "unmuted"]).optional(),
    });
  • src/index.ts:194-199 (registration)
    Registration of the tool with name 'get_service_accounts', including its description and inputSchema referencing ServiceAccountFiltersSchema.
    {
      name: "get_service_accounts",
      description:
        "Return a list of accounts for a specific service. The serviceId can be obtained from the get_services tool. Can be searched by email/name of the account by keyword",
      inputSchema: zodToJsonSchema(ServiceAccountFiltersSchema),
    },
  • src/index.ts:313-313 (registration)
    Tool handler registration mapping the 'get_service_accounts' name to the getServiceAccounts function with schema validation via ServiceAccountFiltersSchema.parse.
    get_service_accounts: async (input) => getServiceAccounts(ServiceAccountFiltersSchema.parse(input)),
Behavior2/5

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

No annotations provided, and the description omits key behavioral details such as pagination, sorting, and the read-only nature of the operation.

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 concise, front-loaded sentences that efficiently convey the core action.

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

Completeness1/5

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

For a tool with 20 parameters and no output schema or annotations, the description is far too brief to enable proper usage.

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

Parameters1/5

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

With 0% schema coverage and 20 parameters, the description only explains serviceId and keyword, leaving the vast majority of parameters unexplained.

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 it returns a list of accounts for a specific service, which distinguishes it from sibling tools like get_identities or get_people_accounts.

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

Usage Guidelines4/5

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

Provides guidance on obtaining the required serviceId from get_services and mentions keyword search, but lacks explicit when-to-use vs alternatives.

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