Skip to main content
Glama
ambaloo

invoiceninja-mcp

by ambaloo

create_client

Create a new client in Invoice Ninja with required name and contacts, plus optional address, tax, and notes.

Instructions

Create a new client

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesClient/company name
contactsYesClient contacts (at least one required)
address1NoStreet address
address2NoAddress line 2
cityNoCity
stateNoState/Province
postal_codeNoPostal/ZIP code
country_idNoCountry ID
phoneNoPhone number
websiteNoWebsite URL
vat_numberNoVAT/Tax number
public_notesNoNotes visible to client
private_notesNoInternal notes
currency_idNoCurrency ID (e.g., '1' for USD)
Behavior2/5

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

No annotations provided, and the description only states 'Create a new client' without disclosing behavioral traits such as idempotency, side effects, or required permissions.

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 sentence, no wasted words. Concise and front-loaded, but could benefit from more detail given the tool's parameter count.

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?

With 14 parameters and no output schema or annotations, the description is too minimal to provide complete context for proper tool usage.

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?

Input schema has 100% description coverage for all 14 parameters, so the description adds no additional meaning beyond what schema already provides.

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 'Create a new client' clearly states the action (create) and the resource (client), distinguishing it from siblings like create_invoice or create_product.

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 on when to use vs alternatives. The description lacks context for prerequisites or exclusions, leaving the agent to infer 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/ambaloo/invoiceninja-mcp'

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