Skip to main content
Glama

get_integration_config

Retrieve a company's integration configuration by its unique ID. Access billing setup details needed for subscription management.

Instructions

Get company integration config by ID. GET /integrations/{integrationId}/config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
integrationIdYesCompany integration ID (required)

Implementation Reference

  • The handler function that executes the tool logic: validates input via Zod schema, then calls integrationService.getIntegrationConfig(client, integrationId) and wraps the result via handleToolCall.
    async function handler(client: Client, args: Record<string, unknown> | undefined) {
      const parsed = schema.safeParse(args);
      if (!parsed.success) {
        return errorResult(parsed.error.errors.map((e) => e.message).join("; "));
      }
      return handleToolCall(() =>
        integrationService.getIntegrationConfig(client, parsed.data.integrationId)
      );
    }
  • Zod schema for input validation: expects a required 'integrationId' string.
    const schema = z.object({
      integrationId: z.string().min(1, "integrationId is required (company integration ID)"),
    });
  • Tool definition object exported as 'getIntegrationConfigTool', combining the definition and handler.
    export const getIntegrationConfigTool: Tool = {
      definition,
      handler,
    };
  • The underlying service function: performs the HTTP GET /integrations/{integrationId}/config call.
    export async function getIntegrationConfig(
      client: Client,
      integrationId: string
    ): Promise<unknown> {
      return client.get<unknown>(`/integrations/${integrationId}/config`);
    }
  • The tool is registered alongside other integration tools in the registerIntegrationTools() function (line 19).
    export function registerIntegrationTools(): Tool[] {
      return [
        listIntegrationsTool,
        getIntegrationConfigTool,
        getIntegrationByKeyTool,
        listIntegrationsByKeyTool,
        listExternalInvoicesTool,
        listExternalProductsTool,
        getExternalProductTool,
        listOrderStatusesTool,
      ];
    }
Behavior2/5

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

With no annotations, the description must disclose behavior; it only mentions it's a GET request but lacks details on authentication, rate limits, or what 'config' entails.

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?

Extremely concise, two sentences with front-loaded verb and resource, no superfluous text.

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

Completeness3/5

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

Adequate for a simple get with one required param, but lacks explanation of return value and behavioral context, making it average.

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

Parameters3/5

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

Schema coverage is 100% with clear parameter description; the description adds no extra meaning beyond schema, so baseline 3.

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 clearly states the action (Get) and resource (company integration config) and specifies the HTTP method and path, distinguishing it from siblings like get_integration_by_key.

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 versus alternatives, no context or exclusions provided.

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/rhinosaas/rebillia-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server