Skip to main content
Glama
iaptic

Iaptic MCP Server

Official
by iaptic

iaptic_current_app

Retrieve the active Iaptic app name and verify credential configuration.

Instructions

Get information about the currently active Iaptic app.

  • Returns the current app name

  • Indicates whether using default or custom credentials

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler that executes the 'iaptic_current_app' tool logic. It calls this.api.getCurrentAppInfo() and returns a text response with the current app name, credential type, and whether a master key is being used.
    case 'iaptic_current_app': {
      const appInfo = this.api.getCurrentAppInfo();
      return {
        content: [{
          type: "text",
          text: `Current app: ${appInfo.appName} (${appInfo.isDefault ? 'default' : 'custom'} credentials, ${appInfo.usingMasterKey ? 'using master key' : 'using app-specific API key'})`
        }]
      };
    }
  • Schema/registration definition for the 'iaptic_current_app' tool. It has no input parameters (empty properties) and provides a description of what the tool does.
          {
            name: "iaptic_current_app",
            description: `Get information about the currently active Iaptic app.
    - Returns the current app name
    - Indicates whether using default or custom credentials`,
            inputSchema: {
              type: "object",
              properties: {}
            }
  • src/tools/app.ts:12-63 (registration)
    The 'getTools()' method in AppTools class registers the tool as part of the available tools list.
      getTools() {
        const appNameRequired = this.isAppNameRequired();
        
        // Base set of tools
        const tools = [
          {
            name: "iaptic_switch_app",
            description: `Switch to a different Iaptic app.
    - Allows temporarily using a different app's credentials
    - All subsequent API calls will use the new app name and API key
    - Useful for managing multiple apps in the same session
    - Required: appName parameter (apiKey required only if not using master key)`,
            inputSchema: {
              type: "object",
              properties: {
                appName: { 
                  type: "string", 
                  description: "Name of the app to switch to" 
                },
                apiKey: { 
                  type: "string", 
                  description: "API key for the app (not required if using master key)" 
                }
              },
              required: ["appName"]
            }
          },
          {
            name: "iaptic_reset_app",
            description: `Reset to the default Iaptic app.
    - Reverts to the original app credentials provided during server initialization
    - All subsequent API calls will use the default app name and API key
    - Use this after using iaptic_switch_app to return to the default app`,
            inputSchema: {
              type: "object",
              properties: {}
            }
          },
          {
            name: "iaptic_current_app",
            description: `Get information about the currently active Iaptic app.
    - Returns the current app name
    - Indicates whether using default or custom credentials`,
            inputSchema: {
              type: "object",
              properties: {}
            }
          }
        ];
        
        return tools;
      }
  • Helper method on IapticAPI that returns information about the currently active app (name, whether it's the default, and whether a master key is being used). This is the underlying data provider for the tool handler.
    getCurrentAppInfo(): { appName: string, isDefault: boolean, usingMasterKey: boolean } {
      return {
        appName: this.appName,
        isDefault: this.appName === this.defaultAppName && this.apiKey === this.defaultApiKey,
        usingMasterKey: !!this.masterKey
      };
    }
Behavior4/5

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

With no annotations provided, the description fully bears the burden of disclosure. It clearly states it returns the current app name and credential type, and there is no indication of side effects or mutations, which is adequate for a read-only tool.

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?

The description is extremely concise, consisting of two bullet points. Every sentence adds value, and there is no superfluous information.

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

Completeness5/5

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

Given the tool's simplicity, no output schema, and no annotations, the description provides complete context. It specifies exactly what is returned (app name, credential type), which is sufficient for an agent.

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?

There are no parameters, and schema coverage is 100%. The description does not need to add parameter information. The baseline for zero parameters is 4, and the description 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?

The description explicitly states it retrieves information about the currently active Iaptic app, including app name and credential type. This is a specific verb-resource combination that distinguishes it from sibling tools like iaptic_reset_app or iaptic_switch_app.

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 does not provide explicit guidance on when to use this tool versus alternatives. However, its simplicity and self-explanatory nature imply it's for querying current app info, but it lacks comparisons to 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/iaptic/mcp-server-iaptic'

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