Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

inventory_feature_options_find

Find feature options for configurable or kit items in Macola inventory, with paging, filtering, and count controls.

Instructions

Find Feature Options (for configurable/kit items).

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
ItemNumberNo
totalCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.1/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 read-only semantics, pagination, default page size, or what a result set contains. Only the implicit "Find" verb hints that this is a non-mutating lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The sentence is short and front-loaded with no wasted words, but its brevity reflects under-specification rather than efficiency given a 10-parameter tool. There is no structure beyond a single clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 10 optional parameters, no annotations, and no output schema, the description is far too thin. An agent would have to guess at filtering, pagination, and return shape before it could invoke this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 10 parameters (page, skip, order, fields, distinct, division, pageSize, countOnly, ItemNumber, totalCount) at 0% description coverage, and the description explains none of them. Pagination, projection, and count-only behaviors are entirely undocumented in both the schema and the description.

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 gives a specific verb ("Find") and a resource ("Feature Options"), plus a parenthetical restricting it to configurable/kit items. However, it never explains what a "feature option" actually is, so an agent unfamiliar with the domain cannot confidently distinguish it from inventory_items_find or inventory_kits_find.

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 explicit when-to-use guidance, no mention of when not to use it, and no reference to the sibling inventory_feature_options_get or any other alternative. The parenthetical hints at a scope but does not tell an agent when to choose this over a get or a broader items search.

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