MCP Cliniko Server

list_invoice_items

Retrieve detailed line items for a specific invoice in the Cliniko healthcare practice management system. Use this tool to view invoice contents, track billing details, and manage financial records within clinical workflows.

Instructions

List items in an invoice (READ-ONLY)

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": {
      "invoice_id": "<invoice_id>"
    },
    "name": "list_invoice_items"
  }
}

Input Schema

Name	Required	Description	Default
`invoice_id`	Yes	Invoice ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 15, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided, so description must cover behavioral traits. '(READ-ONLY)' indicates no side effects, but lacks details on pagination, sorting, error handling, or whether it returns all items or a subset.

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?

Extremely concise—one short phrase. No wasted words, but could be structured as a full sentence to improve readability. Efficient for simple tool.

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?

Given single parameter, no output schema, and no annotations, the description is minimal but adequate. Lacks details on return value structure, error cases, or usage hints. Could be improved with one or two more sentences.

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% (parameter 'invoice_id' documented). Description adds '(READ-ONLY)' but no additional param meaning. Baseline 3 for high coverage.

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?

Description clearly states 'List items in an invoice' with a specific verb and resource, and the '(READ-ONLY)' suffix distinguishes it from mutation tools like create/update/delete. It differentiates from sibling 'list_invoices' by specifying granularity.

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 this tool versus alternatives. Does not mention prerequisites (e.g., must have invoice_id from get_invoice) or context where it is appropriate or not.

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