mcp-server-smallinvoice

list_products

Read-only

Retrieve product records with search, filter, and offset/limit options for efficient data access.

Instructions

Returns list of products

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_products"
  }
}

Input Schema

Name	Required	Description
`with`	No	Comma separated, optional keys that should be included in the response.
`q`	No	Value for full text search
`filter`	No	Filter expression (JSON)
`limit`	No	Limits the number of items returned. Number in a range [1-200]
`offset`	No	Offset of the first item to return. The offset of the initial item is 0.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The annotations already indicate `readOnlyHint=true` and `destructiveHint=false`, so the description adds no new behavioral insight. It does not disclose how pagination works, whether results are sorted, or any side effects, which would be useful beyond the schema.

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, clear sentence. It is concise and front-loaded, but could be slightly more informative 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 has 5 parameters and no output schema, the description is too minimal. It does not explain what fields are returned, how to interpret results, or any default behavior. For a listing tool, this lack of detail reduces 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?

The input schema has 100% coverage with descriptions for all 5 parameters, so the description does not need to add parameter details. It provides no additional semantic meaning beyond 'list of products', but the schema itself is adequate.

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 products' clearly states the action (list) and resource (products). However, among many sibling `list_*` tools, it does not differentiate itself from similar list tools like `list_product_categories` or `get_product`.

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 is provided on when to use this tool versus alternatives. The description gives no context about prerequisites, typical use cases, or when not to use it, which is important given the large number of sibling tools.

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

Deploy Server