Skip to main content
Glama
moneyforward-i

Admina MCP Server

get_organization_info

Retrieve organization details including name, unique name, status, and system language to understand your organization's configuration.

Instructions

Get information about the organization including name, unique name, status, system language, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'get_organization_info' tool logic. It calls the Admina API with an empty endpoint (since the base URL already includes /organizations/{organizationId}) and no query parameters.
    export async function getOrganizationInfo() {
      const client = getClient();
      // The endpoint is just empty string since the base URL already includes /organizations/{organizationId}
      return client.makeApiCall("", new URLSearchParams());
    }
  • Zod input schema for the tool - an empty object since no input parameters are needed (organizationId is handled by the client).
    export const OrganizationInfoSchema = z.object({});
  • src/index.ts:85-89 (registration)
    Tool registration in the ListToolsRequestHandler - declares the tool name 'get_organization_info', description, and binds the input schema.
      name: "get_organization_info",
      description:
        "Get information about the organization including name, unique name, status, system language, etc.",
      inputSchema: zodToJsonSchema(OrganizationInfoSchema),
    },
  • src/index.ts:298-298 (registration)
    Tool handler mapping in the CallToolRequestHandler - maps the tool name string to the handler function getOrganizationInfo().
    get_organization_info: async () => getOrganizationInfo(),
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states it gets information (a read), but discloses no further behavioral traits like authentication needs, side effects, or rate limits. Minimal transparency beyond basic 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?

Single sentence, no wasted words, front-loaded with action and object. Each element contributes to understanding.

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?

For a simple read-only tool with no parameters, the description covers purpose and key output fields. Lacks mention of any potential errors or return format, but no output schema exists. Complete enough for typical use.

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 (100% coverage), so baseline is 4. The description adds value by listing example output fields (name, unique name, status, system language), providing semantic context beyond the empty schema.

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 explicitly states the tool retrieves organization information, listing specific attributes like name, unique name, status, system language. It clearly differentiates from sibling tools focused on identities, devices, or services.

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 retrieving org-level info without parameters, but does not explicitly state when to use or avoid, nor mention alternatives. Given simplicity, it's adequate but lacks explicit guidance.

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