mcp-server-smallinvoice

get_delivery_note

Read-only

Retrieve data for a specific delivery note by providing its ID.

Instructions

Returns data of specified delivery note

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": {
      "delivery_note_id": "<delivery_note_id>"
    },
    "name": "get_delivery_note"
  }
}

Input Schema

Name	Required	Description	Default
`delivery_note_id`	Yes	delivery note ID
`with`	No	Comma separated, optional keys that should be included in the response.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds no extra behavioral context beyond stating the return action. It does not mention authentication, rate limits, or potential side effects, but for a read-only tool this is acceptable.

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?

The description is a single, front-loaded sentence that conveys the essential purpose without any superfluous words. It is perfectly concise and well-structured for quick comprehension.

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?

Given the tool's simplicity (get by ID), the annotated readOnlyHint, and the complete schema, the description is sufficient. It could optionally mention that it returns the full delivery note object, but this is not necessary for agent decision-making. No output schema exists, but for a simple retrieval, the description provides the necessary context.

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%, with both parameters (delivery_note_id and with) well-described in the schema. The description does not add any additional meaning or context beyond what is already provided, so a baseline score of 3 is appropriate.

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 'Returns data of specified delivery note' clearly states the action (returns data) and the resource (delivery note). Among siblings, there are distinct tools like list_delivery_notes and get_delivery_note_preview, so this tool is uniquely identified as a single-item retrieval.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. While it is implied that this tool is for fetching a single delivery note by ID, there is no mention of when not to use it or which sibling tools might be better suited for different contexts.

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

Deploy Server