bokio-mcp

Overview Schema Source Related Servers Discussions Admin

bokio_list_items

Read-only

Lists products and services (items) used on invoice lines with pagination and filtering. Use to browse item catalog for invoice line management.

Instructions

List items (artiklar), the products and services used on invoice lines, with paging. Use bokio_get_item for one item.

Input Schema

Name	Required	Description
`page`	No	Page number (1-based)
`query`	No	Bokio filter query; combine conditions with &&, e.g. "date>=2026-07-01&&date<=2026-07-31"
`pageSize`	No	Items per page (max 100)
`companyId`	No	Bokio company id. Defaults to BOKIO_COMPANY_ID if omitted.

Output Schema

Name	Required	Description	Default
`items`	No
`totalItems`	No
`totalPages`	No
`currentPage`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.4.0Oct 26, 2026
- addedInput schema / properties / companyId / pattern
```
Added value: +"^[A-Za-z0-9_-]+$"
```
- changedInput schema / properties / pageSize / description
```
Previous value: -"Items per page"New value: +"Items per page (max 100)"
```
- changedInput schema / properties / pageSize / maximum
```
Previous value: -200New value: +100
```
- addedInput schema / properties / query
```
Added value: +{
+  "description": "Bokio filter query; combine conditions with &&, e.g. \"date>=2026-07-01&&date<=2026-07-31\"",
+  "type": "string"
+}
```
- removedOutput schema / properties / items / items / additionalProperties
```
Removed value: -{}
```
- removedOutput schema / properties / items / items / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / items / items / type
```
Removed value: -"object"
```
First observedv0.1.0Jul 27, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and scope are covered. The description adds the paging trait and clarifies what an item is, but says nothing about ordering, volume, or filtering behavior beyond paging.

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?

Two short sentences, purpose front-loaded followed by the routing hint. No wasted words.

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?

Output schema and annotations carry return shape and safety, and the description supplies domain meaning plus the sibling route. Slightly incomplete on pagination defaults and query usage, but nothing an agent needs in order to call it is missing.

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%, with page, pageSize, query syntax example, and companyId default all documented in the schema. The description only echoes "with paging," so baseline 3 applies.

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?

States a specific verb and resource ("List items"), defines the domain (products and services used on invoice lines), and notes paging. The parenthetical "artiklar" and the single-item sibling contrast make it easy to distinguish from bokio_get_item.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative explicitly: "Use bokio_get_item for one item," which tells an agent exactly when to pick the sibling instead. This is the correct decision rule for a list-vs-get pair.

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

Deploy Server