Skip to main content
Glama
AaroYazilim

AARO ERP MCP Server

by AaroYazilim

erp_token_sil

Remove cached authentication tokens from the AARO ERP MCP Server to require fresh authentication for subsequent API operations.

Instructions

Cache'deki token'ı siler. Yeni API çağrıları için yeni token alınması gerekecek.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The deleteToken handler deletes the ERP token cache file from disk, returning success or error messages. This is the core logic for the 'erp_token_sil' (ERP token delete) tool, as 'sil' means 'delete' in Turkish and matches the functionality.
    private async deleteToken() {
      try {
        if (fs.existsSync(this.tokenCacheFile)) {
          fs.unlinkSync(this.tokenCacheFile);
          this.log('Token cache başarıyla silindi');
          return {
            content: [{ type: 'text', text: 'Token cache başarıyla silindi. Yeni API çağrıları için yeni token alınması gerekecek.' }],
          };
        } else {
          this.log('Silinecek token cache bulunamadı');
          return {
            content: [{ type: 'text', text: 'Silinecek token cache bulunamadı. Cache zaten boş.' }],
          };
        }
      } catch (error) {
        this.log('Token cache silme hatası', 'error', error);
        return {
          content: [
            {
              type: 'text',
              text: `Token cache silme hatası: ${error instanceof Error ? error.message : 'Bilinmeyen hata'}`,
            },
          ],
          isError: true,
        };
      }
    }
  • The switch case in callSpecialHandler that routes the 'deleteToken' handler call, which corresponds to the erp_token_sil tool.
    case 'deleteToken':
      return await this.deleteToken();
  • The callSpecialHandler method that dispatches to specific handlers based on config, including deleteToken for token deletion.
    private async callSpecialHandler(handlerName: string, args: any) {
      switch (handlerName) {
        case 'getErpToken':
          if (!isValidErpTokenArgs(args)) {
            throw new McpError(ErrorCode.InvalidParams, 'Geçersiz ERP token parametreleri');
          }
          const token = await this.getErpToken(args.password);
          return {
            content: [{ type: 'text', text: `ERP Token başarıyla alındı: ${token}` }],
          };
    
        case 'deleteToken':
          return await this.deleteToken();
    
        case 'addManualToken':
          return await this.addManualToken(args);
    
        case 'createStok':
          return await this.createStok(args);
    
        case 'createCari':
          return await this.createCari(args);
    
        case 'createDekont':
          return await this.createDekont(args);
    
        case 'addDekontKalem':
          return await this.addDekontKalem(args);
    
        case 'updateDekont':
          return await this.updateDekont(args);
    
        case 'testWebhook':
          return await this.testWebhook(args);
    
        case 'callErpApi':
          if (!isValidErpApiArgs(args)) {
            throw new McpError(ErrorCode.InvalidParams, 'Geçersiz API çağrı parametreleri');
          }
          return await this.callErpApi(args.endpoint!, args.method || 'GET', args);
    
        default:
          throw new McpError(ErrorCode.MethodNotFound, `Bilinmeyen handler: ${handlerName}`);
      }
    }
Behavior3/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 discloses the destructive nature (deletes token) and consequence (new token needed for future API calls), which is good behavioral context. However, it doesn't mention authentication requirements, rate limits, or error conditions that might be relevant for a token management 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?

Perfectly concise with two sentences that each earn their place. The first states the action, the second explains the consequence. No wasted words, front-loaded with the core purpose.

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 zero-parameter destructive operation with no annotations or output schema, the description provides good context about what gets destroyed and the consequence. It could be more complete by mentioning authentication requirements or error scenarios, but given the simplicity of the operation (delete token), it's reasonably complete.

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?

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose and consequences. Baseline for 0 parameters is 4.

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 specific action ('siler' - deletes) and resource ('Cache'deki token'ı' - token in cache), distinguishing it from siblings like 'erp_token_al' (get token) and 'erp_token_manuel_ekle' (add token manually). It provides a complete purpose statement with verb+resource+consequence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool ('Yeni API çağrıları için yeni token alınması gerekecek' - new token will be needed for new API calls) and implies when not to use it (when you want to keep the current token active). It distinguishes from sibling 'erp_token_al' which would be the alternative for obtaining a new token after deletion.

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/AaroYazilim/aaro-erp-mcp-server'

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