Skip to main content
Glama
idoklad-mcp

idoklad-mcp

by honzsik

List price list items

list_price_list_items
Read-only

Search price list items by name or code to retrieve prices for creating invoices. Filter by partial name or code and paginate results.

Instructions

Search the price list (ceník) by item name or code. Use the prices when creating invoices.

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

Input Schema

NameRequiredDescriptionDefault
codeNoPart of the item code.
nameNoPart of the item name.
pageNo
pageSizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/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 the safety profile is covered. The description adds only that this searches a Czech-language price list and that the returned prices feed invoicing; it says nothing about matching behavior, empty results, or how many items come back.

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 with the core searchable resource front-loaded and zero filler. Every clause carries information (search target, filter dimensions, intended use).

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?

For a simple read-only list tool with no output schema, the description leaves the return shape vague — an agent does not know whether items, prices, units, or codes are returned, nor how pagination surfaces in the response. It is adequate but incomplete relative to the 4-parameter, no-output-schema definition.

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 50%: the code and name parameters are already documented in the schema as partial matches ('Part of the item code'), which the description merely restates. The pagination parameters (page, pageSize) are undocumented in both schema and description, so no compensation for the coverage gap occurs.

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?

States a specific verb and resource ('Search the price list (ceník)') and names the searchable dimensions (item name or code). An agent can tell it retrieves price-list items and accepts name/code filters, though the description never contrasts it with any sibling tool.

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 sentence 'Use the prices when creating invoices' gives a downstream purpose, implying the tool is for looking up prices before invoicing. However, it offers no explicit when-to-use condition, no prerequisites (e.g. auth or that the price list must be configured), and no alternative routing.

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