Skip to main content
Glama
Sign In
mcp-server-smallinvoice

mcp-server-smallinvoice

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_order_confirmations

Read-only

Retrieve a list of order confirmations from your smallinvoice account. Filter and search to find specific confirmations quickly.

Instructions

Returns list of order confirmations

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": "list_order_confirmations"
  }
}

Input Schema

NameRequiredDescriptionDefault
withNoComma separated, optional keys that should be included in the response.
qNoValue for full text search
filterNoFilter expression (JSON)
limitNoLimits the number of items returned. Number in a range [1-200]
offsetNoOffset of the first item to return. The offset of the initial item is 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations (readOnlyHint=true, destructiveHint=false) already disclose non-destructive read behavior, so the description does not contradict them. However, it adds no additional behavioral context beyond 'Returns list', such as pagination behavior, potential response size, or performance implications.

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?

The description is a single, succinct sentence with no wasted words. It is appropriately front-loaded, but could benefit from slightly more informative content without becoming verbose.

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?

Given the tool's features (pagination, search, filtering, optional fields) inferred from 5 parameters and no output schema, the description is too brief. It does not mention these capabilities, leaving the agent uninformed about how to effectively use the tool beyond basic listing.

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?

With 100% schema description coverage, the parameter meanings are already captured in the schema. The tool description 'Returns list of order confirmations' adds no extra semantic value beyond what the schema provides, earning the baseline score of 3.

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 'Returns list of order confirmations' clearly states the action (list) and resource (order confirmations). However, it does not distinguish this tool from sibling list tools like list_offers or list_invoices, missing an opportunity to clarify its unique context.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., get_order_confirmation for a single record, or create_order_confirmation for entry). It does not mention supported filtering or search parameters, leaving the agent without context for effective selection.

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

Deploy Server

Other Tools