kazaplan-mcp

Overview Schema Source Related Servers Discussions Admin

Kz Catalog Item

kz_catalog_item

Retrieve details for a catalog item (model or material) by ID to support furniture and material selection in 3D home design.

Instructions

Fiche d'un article du catalogue (model-… ou material-…).

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": {
      "item_id": "<item_id>"
    },
    "name": "kz_catalog_item"
  }
}

Input Schema

Name	Required	Description	Default
`item_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about whether this is a read-only lookup, what happens for an unknown item_id (error vs empty), or any access constraints. The output schema does cover the return shape, which relieves some pressure, but the disclosure is still thin.

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?

One compact sentence with no filler, and the distinguishing detail (the ID prefixes) is placed where it is immediately visible. The brevity borders on under-specification, but nothing is wasted.

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?

The tool is simple (one required parameter) and has an output schema explaining return values, so the description need not be long. Still, a single-sentence definition leaves an agent without failure-mode or alternative-selection information that would be cheap to include.

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 0%, so the single item_id parameter is documented nowhere else; the description partially compensates by showing that IDs are prefixed with 'model-…' or 'material-…'. It still does not state whether the full prefixed ID or a bare identifier is expected, so the gap is narrowed but not closed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as a catalog item ('article du catalogue') and implies retrieval of its record ('fiche'), and the parenthetical hints at the ID domain (model-… or material-…). However, there is no explicit verb and no differentiation from the sibling kz_search_catalog, so an agent must infer that this is a point-lookup rather than a search.

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?

There is no guidance on when to use this tool versus kz_search_catalog or the other catalog-related siblings, and no stated prerequisites (e.g. that the item must already exist). The only usage signal is implicit in the parenthetical ID prefixes.

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