Skip to main content
Glama
Invoice Ninja MCP Server

Invoice Ninja MCP Server

by TETRA-2023

List vendors

in_list_vendors
Read-only

List vendors and search expense counterparties with optional filters, pagination, sorting, and status selection to find the records you need.

Instructions

List vendors (expense counterparties) with optional search.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "in_list_vendors"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination.
sortNoSort directive, e.g. 'date|desc'.
filterNoFree-text search across the entity's searchable columns.
statusNoRecord state (default 'active'). 'all' also returns archived and deleted records.
per_pageNoRows per page (capped server-side, default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior2/5

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

readOnlyHint=true already establishes the safety profile, so the description only needs to add context beyond that. It adds essentially none: nothing about the default 'active'-only scoping (a real behavioral subtlety), pagination behavior, or result shape. The 'optional search' phrase merely restates a schema parameter.

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?

A single front-loaded sentence with zero filler, correctly naming the resource first. It is perhaps overly terse for the tool's behavioral nuances, but nothing is wasted.

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

Completeness5/5

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

For a read-only, zero-required-parameter list tool with fully documented schema and no output schema, the description plus structured fields give the agent everything needed to invoke it correctly. Remaining gaps are behavioral nuance, not invocation blockers.

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 baseline is 3. The description only echoes the filter parameter via 'optional search' and adds no meaning about sort syntax, page/per_page defaults, or the status enum, all of which the schema already handles.

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?

States a specific verb and resource (list vendors) and adds a clarifying gloss, 'expense counterparties', that tells the agent these are expense-side entities rather than clients or products. It does not explicitly contrast with siblings like in_list_expenses, but the resource itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'with optional search' hints at the filter path but there is no explicit when-to-use guidance, no statement of when to prefer in_list_expenses or in_get_invoice, and no prerequisites named. Usage is implied by the name rather than taught.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.