Skip to main content
Glama
Cresium

Cresium MCP Server

Official
by Cresium

create_invoices

Generate invoices for accounts receivable to track expected payments from customers. Specify amount, payer details, status, and optional notes.

Instructions

Create one or more invoices (accounts receivable). Each invoice represents an amount the company expects to receive from a customer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
invoicesYesArray of invoice objects to create

Implementation Reference

  • Tool registration and schema definition for 'create_invoices' in the TOOL_DEFINITIONS array. Defines the tool name, description, and input schema including required fields (amount, payerNationalIdentifier, payerName, status) and optional fields for creating invoices (accounts receivable).
    {
      name: "create_invoices",
      description:
        "Create one or more invoices (accounts receivable). Each invoice represents an amount the company expects to receive from a customer.",
      inputSchema: {
        type: "object" as const,
        properties: {
          invoices: {
            type: "array",
            items: {
              type: "object",
              properties: {
                amount: { type: "number", description: "Invoice amount" },
                payerNationalIdentifier: {
                  type: "string",
                  description: "Payer CUIT/CUIL",
                },
                payerName: { type: "string", description: "Payer name" },
                status: {
                  type: "string",
                  enum: ["PENDING", "EXPIRED", "PAID"],
                },
                description: { type: "string" },
                internalNote: { type: "string" },
                payerInternalNote: { type: "string" },
                payerEmail: { type: "string" },
                expiresAt: { type: "string" },
                createdAt: { type: "string" },
                externalId: { type: "string" },
                fileUrl: { type: "string" },
              },
              required: [
                "amount",
                "payerNationalIdentifier",
                "payerName",
                "status",
              ],
            },
            description: "Array of invoice objects to create",
          },
        },
        required: ["invoices"],
      },
    },
  • Handler implementation for 'create_invoices' in the handleToolCall method. Makes a POST request to the /v3/invoice/ API endpoint with the invoices array from the arguments to create one or more invoices (accounts receivable).
    case "create_invoices":
      result = await this.request(
        "POST",
        "/v3/invoice/",
        args.invoices
      );
      break;
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it states this creates invoices (implying a write operation), it doesn't mention permissions required, whether invoices are immediately finalized, how errors are handled, or what the response contains. For a mutation tool with zero annotation coverage, this leaves significant behavioral 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 efficiently structured in two sentences that convey core functionality without waste. The first sentence states the action and scope, while the second explains the business context. Every sentence earns its place, though it could be slightly more front-loaded with key details.

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 mutation tool that creates financial records with no annotations and no output schema, the description is insufficient. It doesn't address what happens after creation, error conditions, validation rules, or return values. The agent lacks critical context needed to use this tool effectively in a real workflow.

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%, so the schema already documents the single 'invoices' parameter and its nested properties. The description adds no additional parameter semantics beyond what's in the schema. The baseline score of 3 reflects adequate coverage through schema alone.

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 creates invoices (accounts receivable) and explains what an invoice represents. It specifies 'one or more invoices' which adds useful scope information. However, it doesn't explicitly differentiate from sibling tools like 'create_payments' or 'list_invoices' beyond the basic verb+resource distinction.

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 like 'create_payments' or 'list_invoices'. There's no mention of prerequisites, appropriate contexts, or exclusions. The agent must infer usage from the tool name alone.

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/Cresium/cresium-mcp-server'

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