Skip to main content
Glama
Sign In
gobox-mcp

gobox-mcp

by Winter279
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_product_skus

List product SKU variants with optional search by SKU code and pagination controls.

Instructions

List all product SKU variants.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch by SKU code
limitNoPage size
pageNoPage number

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so the description carries full burden. It states 'List all' but the input schema includes pagination parameters (limit, page), implying the tool is paginated and does not return all SKUs at once. This contradiction is not disclosed. No mention of authentication, rate limits, or side effects.

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 a single, clear sentence with no unnecessary words. It is front-loaded and efficient, though it omits important behavioral details.

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

Completeness2/5

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

Given the presence of pagination and a search parameter, the description should clarify that results are paginated and optionally filterable. It fails to convey these critical usage constraints. Output schema exists but does not compensate for missing behavioral context.

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 100%, so baseline is 3. The description adds no additional meaning beyond the schema. The 'q' parameter allows search by SKU code, but the description 'List all' conflicts with this capability.

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?

The description 'List all product SKU variants' clearly states the action (list) and resource (product SKU variants). It is specific, but does not distinguish from the sibling tool 'search_all_product_skus', which likely offers more extensive filtering. Thus, purpose is clear but lacks differentiation.

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?

No guidance on when to use this tool versus alternatives like 'search_all_product_skus' or other listing tools. The description provides no context for appropriate usage scenarios, leaving the agent to infer.

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