Skip to main content
Glama
iaptic

Iaptic MCP Server

Official
by iaptic

iaptic_reset_app

Reverts to the original app credentials from server initialization, restoring default app name and API key for subsequent API calls.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for iaptic_reset_app tool: calls this.api.resetToDefaultApp() and returns success message
    case 'iaptic_reset_app':
      this.api.resetToDefaultApp();
      return {
        content: [{
          type: "text",
          text: `Successfully reset to default app`
        }]
      };
  • Schema registration for iaptic_reset_app: defines the tool name, description, and empty input schema
          {
            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: {}
            }
          },
  • Helper method resetToDefaultApp() in IapticAPI class: resets apiKey and appName to defaults and reinitializes the HTTP client
    // Method to reset to the default app
    resetToDefaultApp(): void {
      this.apiKey = this.defaultApiKey;
      this.appName = this.defaultAppName;
      this.initializeClient();
      console.error(`Reset to default app: ${this.appName}`);
    }
  • src/server.ts:108-110 (registration)
    Registration in server.ts: routes tools starting with 'iaptic_' to app.handleTool(), which handles iaptic_reset_app
    if (name.startsWith('iaptic_')) {
      return await this.tools.app.handleTool(name, args);
    }
Behavior3/5

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

Description explains the effect (reverts credentials, subsequent calls use default) but lacks details on safety or side effects. With no annotations, it carries full burden; a more detailed behavioral disclosure would improve this score.

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?

Three bullet points, front-loaded with main action, no unnecessary words. Every sentence adds value.

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 no output schema and simple reset action, description covers purpose, usage, and effect fully. No gaps identified.

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?

No parameters in schema; description correctly omits parameter info. Baseline score of 4 applies as the description adds no parameter semantics 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?

Description clearly states 'Reset to the default Iaptic app' with specific verb and resource, and distinguishes from sibling tools like iaptic_switch_app by explicitly mentioning reverting credentials.

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?

Description provides explicit usage context: 'Use this after using iaptic_switch_app to return to the default app'. It does not explicitly state when not to use, but the sibling tools provide implicit 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/iaptic/mcp-server-iaptic'

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