Skip to main content
Glama
Sign In
clover-mcp

clover-mcp

by SBolivarLoL
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_attributes

Read-only

Retrieve item attributes (variant axes like Size/Color) with their available options for inventory management. Requires INVENTORY_R permission.

Instructions

Return item attributes (variant axes like Size/Color) with options. Requires INVENTORY_R.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint annotation is consistent with the 'Return' wording, and the description adds the INVENTORY_R authorization requirement, which is not visible in the annotations. It also clarifies that the result includes 'options' (the attribute's possible values), adding behavioral context.

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

Conciseness5/5

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

Two sentences with no filler; the purpose is front-loaded in the first sentence, and the permission note is a compact second sentence.

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?

For a read-only, parameterless tool with output schema and annotations, the description covers purpose, permission, and return content sufficiently. No additional details are needed for correct invocation.

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

Parameters4/5

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

The tool has no parameters, so the description does not need to explain parameter syntax. The baseline for a zero-parameter tool is 4, and the description adds relevant context about the return content.

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 uses the specific verb 'Return' and names the resource 'item attributes', with concrete examples (variant axes like Size/Color). This clearly distinguishes it from sibling list tools like list_items or list_categories.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a clear permission requirement (INVENTORY_R) but does not specify when to choose this tool over alternatives, nor does it mention any exclusions. Usage is implied (when needing attribute axes), but there is no explicit guidance.

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