Skip to main content
Glama
AaroYazilim

AARO ERP MCP Server

by AaroYazilim

erp_stok_olustur

Create new stock items in the ERP system with required codes and names, then generate direct links to view the created items.

Instructions

ERP sisteminde yeni stok kartı oluşturur. oluşturduktan sonra https://erp.aaro.com.tr/Stok/Kalem?id={id} kullanıcıya bu linki sunabilir

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
StokKoduYesStok kodu (zorunlu)
StokAdiYesStok adı (zorunlu)
StokKisaKoduNoStok kısa kodu
StokKisaAdiNoStok kısa adı
TipIDNoStok tipi (varsayılan: 105001)
SubeIDNoŞube ID (varsayılan: 1)
SirketIDNoŞirket ID (varsayılan: 1)
Brm1IDNoBirim ID (varsayılan: 1 - Adet)
StokMuhasebeIDNoMuhasebe ID
DurumNoAktif/Pasif durumu (varsayılan: true)

Implementation Reference

  • Handler function for creating a new ERP stock item (stok oluştur). Takes parameters like StokKodu, StokAdi etc., constructs payload and calls /api/Stok POST. This is the core implementation logic for the 'erp_stok_olustur' tool.
    private async createStok(args: any) {
      const { StokKodu, StokAdi, StokKisaKodu, StokKisaAdi, TipID, SubeID, SirketID, Brm1ID, StokMuhasebeID, Durum, ...otherParams } = args;
      
      if (!StokKodu || !StokAdi) {
        throw new Error('StokKodu ve StokAdi gerekli');
      }
    
      const stokData = {
        StokID: -1, // Yeni kayıt için -1
        StokKodu,
        StokAdi,
        StokKisaKodu: StokKisaKodu || StokKodu,
        StokKisaAdi: StokKisaAdi || StokAdi,
        TipID: TipID || '105001', // Varsayılan stok tipi
        SubeID: SubeID || '1',
        SirketID: SirketID || '1',
        Brm1ID: Brm1ID || '1', // Varsayılan birim: Adet
        StokMuhasebeID: StokMuhasebeID || '201',
        Durum: Durum !== undefined ? Durum : true,
        ...otherParams
      };
    
      return await this.callErpApi('/api/Stok', 'POST', {
        KayitTipi: '1', // Yeni kayıt
        body: stokData
      });
    }
  • src/index.ts:236-237 (registration)
    Registration of the 'createStok' handler in the special handlers switch statement. Tool configs in tools.json likely map 'erp_stok_olustur' to handler: 'createStok'.
    return await this.createStok(args);
  • Uses the callErpApi helper to perform the actual API call to create stock.
      return await this.callErpApi('/api/Stok', 'POST', {
        KayitTipi: '1', // Yeni kayıt
        body: stokData
      });
    }
  • src/index.ts:167-174 (registration)
    Dynamic tool registration and listing from loaded tools.json config, where 'erp_stok_olustur' is expected to be defined with handler: 'createStok'.
      const tools = Object.entries(this.toolsConfig).map(([name, config]) => ({
        name,
        description: config.description,
        inputSchema: config.inputSchema,
      }));
    
      return { tools };
    });
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 for behavioral disclosure. It states the tool creates a stock card and mentions providing a URL afterward, which hints at a successful creation response. However, it doesn't cover critical behavioral aspects: required permissions, whether the operation is idempotent, error conditions, rate limits, or what happens if duplicate stock codes are used. For a creation tool with 10 parameters, this leaves significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences that directly address core functionality. The first sentence states the primary action, and the second provides useful operational context about the response URL. There's no unnecessary verbiage, though it could be slightly more structured by separating behavioral details from the purpose statement.

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

Completeness2/5

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

For a creation tool with 10 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns beyond implying an ID is generated for the URL. It lacks information about error handling, authentication requirements, and the relationship between parameters (e.g., how TipID affects the created record). The description should provide more context about the creation operation's behavior and outcomes.

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 description coverage is 100%, with each parameter documented in the schema (e.g., 'StokKodu' as mandatory stock code, 'TipID' with default value 105001). The description adds no parameter-specific information beyond what's already in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'ERP sisteminde yeni stok kartı oluşturur' (creates a new stock card in the ERP system). It specifies the verb ('oluşturur' - creates) and resource ('stok kartı' - stock card), making the action explicit. However, it doesn't differentiate from sibling tools like 'erp_cari_olustur' (create customer) or 'erp_dekont_olustur' (create voucher), which follow similar creation patterns.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication), distinguish it from similar creation tools in the sibling list, or indicate scenarios where this tool is preferred over others. The second sentence about providing a URL to the user is operational rather than usage 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/AaroYazilim/aaro-erp-mcp-server'

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