Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

inventory_feature_options_get

Retrieve a specific inventory feature option by its ID to inspect configuration details for a Macola inventory entry.

Instructions

Get the Feature Option for a particular entry by specifying its ID.

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": {
      "id": "<id>"
    },
    "name": "inventory_feature_options_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFeature option ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about what happens when the ID does not exist, whether the call is read-only, permission requirements, or what the response contains. "Get" weakly implies a read, but that is inference rather than disclosure.

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?

A single short sentence with no filler, and the key information (resource + ID lookup) is front-loaded. It is efficient, though its brevity reflects thin content rather than disciplined editing.

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 one-parameter read tool with no output schema, the description covers the minimum needed to invoke it correctly. It leaves gaps around not-found behavior and what a Feature Option record contains, which an agent would need to interpret results.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already documents the id field. The description's "by specifying its ID" merely restates the schema, which is the baseline 3 case.

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 ("Get") and resource ("Feature Option") plus the retrieval key (ID), which is enough to distinguish a single-record fetch from a list/search. It stops short of naming the sibling inventory_feature_options_find, so the get-vs-find distinction is only implied by "by specifying its ID".

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 to prefer inventory_feature_options_find, and no prerequisites or error conditions. The only usage signal is the implicit 'single record by ID' framing.

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