Skip to main content
Glama
Sign In
@ktmcp/beezup

@ktmcp/beezup

by ktmcp-cli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

GetUserListOfValues

Retrieve the list of values associated with a specified list name in BeezUP for managing store configuration.

Instructions

Get the list of values related to this list name

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": {
      "listName": "<listName>"
    },
    "name": "GetUserListOfValues"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNameYesThe list of value name your want to get

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior1/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'Get,' implying a read operation, but does not confirm idempotency, permissions needed, rate limits, or side effects. This is a critical gap for a tool with no annotation support.

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?

The description is a single, well-formed sentence that front-loads the core action. Every word is necessary; no redundancy or filler. Concise and efficient.

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?

Given the tool's simplicity (one parameter, no output schema), the description is minimally adequate. It identifies the input and action but does not explain the nature of 'list of values,' possible return formats, or error conditions. For a straightforward getter, this may suffice, but lacks richness.

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% (the only parameter 'listName' has a schema description). The tool description adds minimal extra meaning: 'related to this list name' mirrors the schema's 'The list of value name your want to get.' No additional semantic value is provided beyond the schema.

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 clearly states the action and object: 'Get the list of values related to this list name.' It specifies a resource ('list of values') and a key ('list name'). However, it does not differentiate from the sibling tool 'GetPublicListOfValues,' which presumably retrieves public lists, missing a chance to clarify scope.

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 is provided on when to use this tool versus alternatives like GetPublicListOfValues or GetUserLovIndex. The description does not mention prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.

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