Skip to main content
Glama

get_doctypes

Retrieve all available document types from ERPNext to understand data structures and access options for system integration.

Instructions

Get a list of all available DocTypes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'get_doctypes' tool within the CallToolRequestSchema switch statement. It verifies authentication, calls erpnext.getAllDocTypes() to retrieve the list, and returns it as formatted JSON or an error message.
    case "get_doctypes": {
      if (!erpnext.isAuthenticated()) {
        return {
          content: [{
            type: "text",
            text: "Not authenticated with ERPNext. Please configure API key authentication."
          }],
          isError: true
        };
      }
      
      try {
        const doctypes = await erpnext.getAllDocTypes();
        return {
          content: [{
            type: "text",
            text: JSON.stringify(doctypes, null, 2)
          }]
        };
      } catch (error: any) {
        return {
          content: [{
            type: "text",
            text: `Failed to get DocTypes: ${error?.message || 'Unknown error'}`
          }],
          isError: true
        };
      }
    }
  • src/index.ts:325-332 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining the tool name, description, and empty input schema (no parameters required).
    {
      name: "get_doctypes",
      description: "Get a list of all available DocTypes",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • Input schema for the get_doctypes tool: an empty object, indicating no input parameters are required.
    inputSchema: {
      type: "object",
      properties: {}
    }
  • ERPNextClient method implementing the core logic to fetch all available DocTypes from the ERPNext API, with fallback methods and a hardcoded list of common DocTypes.
      async getAllDocTypes(): Promise<string[]> {
        try {
          // Use the standard REST API to fetch DocTypes
          const response = await this.axiosInstance.get('/api/resource/DocType', {
            params: {
              fields: JSON.stringify(["name"]),
              limit_page_length: 500 // Get more doctypes at once
            }
          });
          
          if (response.data && response.data.data) {
            return response.data.data.map((item: any) => item.name);
          }
          
          return [];
        } catch (error: any) {
          console.error("Failed to get DocTypes:", error?.message || 'Unknown error');
          
          // Try an alternative approach if the first one fails
          try {
            // Try using the method API to get doctypes
            const altResponse = await this.axiosInstance.get('/api/method/frappe.desk.search.search_link', {
              params: {
                doctype: 'DocType',
                txt: '',
                limit: 500
              }
            });
            
            if (altResponse.data && altResponse.data.results) {
              return altResponse.data.results.map((item: any) => item.value);
            }
            
            return [];
          } catch (altError: any) {
            console.error("Alternative DocType fetch failed:", altError?.message || 'Unknown error');
            
            // Fallback: Return a list of common DocTypes
            return [
              "Customer", "Supplier", "Item", "Sales Order", "Purchase Order",
              "Sales Invoice", "Purchase Invoice", "Employee", "Lead", "Opportunity",
              "Quotation", "Payment Entry", "Journal Entry", "Stock Entry"
            ];
          }
        }
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves a list but doesn't specify if the list is paginated, sorted, or includes metadata. It also omits details like authentication requirements, rate limits, or whether the data is cached, leaving gaps in understanding how the tool behaves.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse quickly. There is no wasted text, earning its place clearly.

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?

Given the tool's simplicity (no parameters, no output schema), the description is adequate but minimal. It covers the basic purpose but lacks details on output format, error handling, or integration with sibling tools. For a read-only list operation, more context on what the list contains (e.g., names, IDs, metadata) would enhance completeness.

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 zero parameters, and the schema description coverage is 100%, meaning there are no undocumented inputs. The description appropriately doesn't discuss parameters, as none exist, so it meets the baseline expectation without needing to compensate for gaps.

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 action ('Get a list') and resource ('all available DocTypes'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_doctype_fields' or 'get_documents' which also retrieve information about DocTypes or documents, leaving room for potential confusion about scope.

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 is provided on when to use this tool versus alternatives. For example, it doesn't clarify if this should be used before 'create_document' to validate DocTypes or how it differs from 'get_doctype_fields' for retrieving field information. The description lacks context about prerequisites or typical use cases.

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/rakeshgangwar/erpnext-mcp-server'

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