Skip to main content
Glama
moneyforward-i

Admina MCP Server

get_services

List services with account previews, filterable by keyword, with pagination and sorting options.

Instructions

Return a list of services, along with the preview of the accounts. Can be searched by the service name by keyword

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
cursorNo
keywordNo
sortByNo
sortOrderNo

Implementation Reference

  • Main handler function 'getServices' that makes an API call to '/services' with parsed query filters. Also contains the 'ServiceFiltersSchema' Zod schema for input validation.
    import { z } from "zod";
    import { getClient } from "../admina-api.js";
    import { filtersToParams } from "../common/helper.js";
    
    export const ServiceFiltersSchema = z.object({
      limit: z.number().optional(),
      cursor: z.string().optional(),
      keyword: z.string().optional(),
      sortBy: z.string().optional(),
      sortOrder: z.string().optional(),
    });
    
    export type ServiceFilters = z.infer<typeof ServiceFiltersSchema>;
    
    export async function getServices(filters: ServiceFilters) {
      const client = getClient();
      const queryParams = filtersToParams(filters);
      return client.makeApiCall("/services", queryParams);
    }
  • Input schema 'ServiceFiltersSchema' defining optional fields: limit, cursor, keyword, sortBy, sortOrder.
    export const ServiceFiltersSchema = z.object({
      limit: z.number().optional(),
      cursor: z.string().optional(),
      keyword: z.string().optional(),
      sortBy: z.string().optional(),
      sortOrder: z.string().optional(),
    });
  • src/index.ts:189-193 (registration)
    Tool registration in the ListToolsRequestSchema handler where 'get_services' is defined with name, description, and inputSchema.
      name: "get_services",
      description:
        "Return a list of services, along with the preview of the accounts. Can be searched by the service name by keyword",
      inputSchema: zodToJsonSchema(ServiceFiltersSchema),
    },
  • src/index.ts:312-312 (registration)
    Tool handler mapping in the toolHandlers record, routing 'get_services' to the getServices function with schema parsing.
    get_services: async (input) => getServices(ServiceFiltersSchema.parse(input)),
  • Helper function 'filtersToParams' used by getServices to convert filter objects to URLSearchParams for the API call.
    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;
    }
Behavior2/5

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

No annotations provided, so description should fully disclose behavior. It mentions return type and search capability but omits pagination, sorting, and side effects. Incomplete for a read tool.

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

Conciseness3/5

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

Two sentences, no wasted words, but lacks structure. Could be improved by grouping related info.

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?

With 5 parameters, no output schema, and no annotations, the description should provide more context on pagination, sorting, and output format. Insufficient for adequate tool use.

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?

Schema coverage is 0%. Description only explains the 'keyword' parameter partially. Does not cover limit, cursor, sortBy, sortOrder. Adds minimal value beyond the schema.

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 the tool returns a list of services with account previews, and mentions keyword search. It distinguishes from siblings like get_service_accounts, but does not explicitly differentiate.

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?

No guidance on when to use this tool vs alternatives. Does not mention prerequisites or use cases beyond keyword search.

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