Skip to main content
Glama
kmexnx
by kmexnx

get_invoice_template

Retrieve the current invoice template structure to understand available fields and formatting for creating professional invoices.

Instructions

Get the current invoice template structure for reference

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that returns the schema/structure definition for an invoice.
    export function getInvoiceTemplate() {
      return {
        description: "Invoice template structure for generating professional invoices",
        requiredFields: {
          company: {
            name: "string - Company name",
            address: "string - Street address",
            city: "string - City name", 
            state: "string - State/Province",
            zipCode: "string - ZIP/Postal code"
          },
          billTo: {
            name: "string - Client name",
            address: "string - Client street address",
            city: "string - Client city",
            state: "string - Client state/province", 
            zipCode: "string - Client ZIP/postal code"
          },
          invoiceNumber: "string - Unique invoice identifier",
          date: "string - Invoice date (YYYY-MM-DD format recommended)",
          items: "array - List of invoice line items with description and amount"
        },
        optionalFields: {
          company: {
            phone: "string - Company phone number",
            fax: "string - Company fax number",
            email: "string - Company email address"
          },
          billTo: {
            company: "string - Client company name",
            phone: "string - Client phone number"
          },
          dueDate: "string - Payment due date",
          taxRate: "number - Tax rate as percentage (e.g., 8.5 for 8.5%)",
          other: "number - Additional fees or discounts"
        },
        itemStructure: {
          description: "string - Description of the service/product",
          amount: "number - Amount in dollars (e.g., 100.50)"
        },
        exampleUsage: {
          company: {
            name: "Acme Corporation",
            address: "123 Business St",
            city: "Business City",
            state: "CA",
            zipCode: "90210",
            phone: "(555) 123-4567",
            email: "billing@acme.com"
          },
          billTo: {
            name: "John Smith",
            company: "Client Corp",
            address: "456 Client Ave",
            city: "Client City", 
            state: "NY",
            zipCode: "10001",
            phone: "(555) 987-6543"
          },
          invoiceNumber: "INV-2024-001",
          date: "2024-08-18",
          dueDate: "2024-09-17",
          items: [
            {
              description: "Web Development Services",
              amount: 2500.00
            },
            {
              description: "Hosting Setup",
              amount: 150.00
            }
          ],
          taxRate: 8.5,
          other: 0
        }
      };
    }
Behavior2/5

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

No annotations provided, so description must carry full burden. While 'Get' implies read-only and 'current' suggests temporal relevance, the description fails to disclose side effects, authentication requirements, rate limits, or what the 'structure' actually contains (fields, schema, etc.).

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?

Single 9-word sentence is appropriately front-loaded with the action verb. However, given the absence of annotations and output schema, the extreme brevity leaves significant gaps rather than demonstrating efficient completeness.

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?

With no output schema and no annotations, the description should specify what the template structure includes or its format. 'Structure for reference' is vague and insufficient for an agent to predict the return value or utility of calling this tool before creating PDFs.

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?

Input schema has 0 parameters with 100% coverage. Per guidelines, 0 params = baseline 4. The description does not mention parameters (none exist), which is appropriate.

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?

Uses specific verb 'Get' and resource 'invoice template structure'. Clearly identifies the operation and target resource, though it does not explicitly differentiate from siblings 'create_invoice_pdf' or 'send_invoice_email' in the description text (distinction relies on tool names).

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?

Provides no guidance on when to use this tool versus the sibling tools. No mention of workflow sequence (e.g., whether to call this before create_invoice_pdf) or prerequisites. The phase 'for reference' hints at read-only usage but doesn't establish clear usage boundaries.

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/kmexnx/invoice-mcp-server'

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