Skip to main content
Glama

kubik-tools

by io.github.markopolovic

Resolve Article Quantities

resolve_quantities

Resolves an ordered quantity of a Library article into concrete packed units (boxes/pallets), using that article's own logged packing history -- never a generic guess.

Check resolution_status first: "resolved" means units/tier are a real answer, safe to use directly. "ambiguous" means the article has more than one viable packaging family (e.g. logged both as pallets and as crates) with meaningfully different pack counts -- units and tier are both null, and alternatives lists every viable option with no default among them. When resolution_status is "ambiguous", do not select an alternative autonomously -- present the options to the user and ask which packaging family they mean; do not guess based on which one appears first. "not_found" means the article has no packed-form data logged at all -- there is nothing to resolve, alternatives is absent, and units/tier are null. needs_confirmation (boolean) is kept only for backward compatibility with callers written before resolution_status existed -- new integrations should check resolution_status.

When resolution_status is "resolved", tier is one of: "observed" (an exact match against a real logged pack), "estimated" (interpolated between two real logged points), or "verify" (extrapolated beyond the highest -- or below the lowest -- quantity ever actually logged for this article; still returns a real number, but flagged as needing a human's eyes before it's trusted).

Does not resolve prepack-table or consolidation-group quantities -- those use the same tier engine but a different lookup key (a table/group id, not a free-text article search) and are not covered by this tool.

Requires an MCP API key (Authorization: Bearer ) issued for a kubik.tools team. Looks the article up by article number or name within that team's own Library -- never across teams.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYesYour team's kubik.tools MCP API key (kubik_mcp_...). Required.
quantityYesThe ordered quantity to resolve, in whole units of the article. Must be a positive number.
article_queryYesThe article number or name to search for in the Library, e.g. 'MLB1001' or 'rim holder'.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

The description explains in detail the resolution_status values ('resolved', 'ambiguous', 'not_found') and what each means, including how to handle 'ambiguous' (present options to the user, not guess). It also describes tier values ('observed', 'estimated', 'verify') with their implications and notes the backward-compatibility needs_confirmation field, providing rich behavioral context beyond the sparse annotations.

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?

The description is long but well-structured, with clear sections for purpose, status handling, tiers, exclusions, and auth. Every sentence adds necessary behavioral detail, though the backward-compatibility note could be trimmed; it is not as tight as a two-sentence description but remains efficient for the complexity.

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

Completeness5/5

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

Given there is no output schema and only three parameters, the description effectively explains all return semantics (units, tier, alternatives, needs_confirmation) and when they apply. It also covers exclusion cases and authentication, making it highly complete for a tool with this complexity.

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 100% for all three parameters, so the schema carries the load. The description adds minor context about the api_key (team-scoped Bearer token) and article_query (looks up by number or name within the team's Library), but largely repeats schema information, so it does not significantly raise the baseline.

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?

The description clearly states a specific verb and resource: 'Resolves an ordered quantity of a Library article into concrete packed units (boxes/pallets)' and explicitly distinguishes from a sibling concern by excluding prepack-table and consolidation-group quantities. It provides a concrete outcome and avoids any tautology.

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?

The description gives explicit guidance: check resolution_status first, do not autonomously choose when ambiguous, and clarifies that prepack/consolidation quantities use a different tool. It also states the API key requirement and team scoping, which are actionable usage prerequisites.

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

All kubik-tools toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation4/5

Most tools have clearly distinct purposes: the freight calculation tools are separated by volume-weight, floor-space, and vehicle-fit outputs, and the Library tools are split into create, search, list, log, resolve, and undo actions. The only mild ambiguity is between resolve_quantities and resolve_prepack_quantities, and between calculate_loading_metres and check_truck_fit, but the descriptions explicitly steer the agent to the right tool.

Naming Consistency5/5

All tool names follow a consistent verb_object pattern in snake_case: calculate, check, create, search, list, log, resolve, undo. Despite some verbs being semantically close, the naming is predictable and internally consistent.

Tool Count5/5

Ten tools is well-scoped for the freight-and-logistics domain the server covers: three calculation/fit tools and seven article-observation/resolution tools. Each tool earns its place, and the set is neither bloated nor too thin.

Completeness4/5

The core workflow is covered: freight calculations, article profile creation/search, packing observation logging, and quantity resolution. Minor gaps remain in lifecycle management—there is no update/delete for article profiles and no MCP tool for creating/list consolidation groups or prepack tables, which pushes some flows back into the external app.

Resources