Skip to main content
Glama
Invoice Ninja MCP Server

Invoice Ninja MCP Server

by TETRA-2023

Get expense

in_get_expense
Read-only

Retrieve a single expense by its hashed ID to view all fields, record state (active, archived, or deleted), and attached documents, with optional side-loading of vendor or category relationships.

Instructions

Fetch a single expense by id: every field, its record state (active/archived/deleted) and its attached documents.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesExpense id (hashed string id, not the display number).
includeNoRelationships to side-load, e.g. 'vendor,category'. Documents always come back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds real context beyond that by saying the response carries every field, includes the record state (active/archived/deleted), and always attaches documents. The archived/deleted disclosure is important because it tells the agent this lookup is not filtered to live records.

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?

A single front-loaded sentence with no filler; the identity, scope, and return contents are packed in without redundancy.

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

Completeness4/5

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

For a two-parameter lookup with no output schema, the description covers what comes back (all fields, record state, documents), which is the main unknown. It omits error behavior when the id is not found, a minor gap given the schema's completeness.

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 coverage is 100%, so both parameters are already documented in the schema, including that the id is a hashed string and that documents always return. The description adds no syntax or format detail beyond that, which is the expected baseline when the schema carries the load.

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 states a specific verb and resource ('Fetch a single expense by id') with the scope constraint (single, by id) that separates it from the list_expenses siblings. It does not name a sibling explicitly, but the singular lookup framing 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?

Usage is only implied: call this when you already have an expense id and need the full record. There is no explicit when-not guidance and no alternative named (e.g., in_list_expenses for browsing), so an agent must infer the routing.

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