Skip to main content
Glama
Sign In
@ktmcp/beezup

@ktmcp/beezup

by ktmcp-cli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

GetAutomaticTransitions

Retrieve a list of automatic order status transitions configured for a specific store. Filter by store ID to view transition rules.

Instructions

Get list of configured automatic Order status transitions

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": "GetAutomaticTransitions"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeIdNoThe StoreId to filter by

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description should fully convey behavioral traits, but it only states the tool 'gets a list'. It does not disclose if the list is paginated, whether the optional storeId parameter is required for filtering, or any side effects. The description is too minimal to understand the tool's behavior beyond its basic function.

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 efficiently concise: one sentence that communicates the core purpose. It is front-loaded and contains no unnecessary words. However, it could include slightly more detail without harming conciseness.

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 lack of output schema and annotations, the description is incomplete. It does not explain what the returned list contains (e.g., transition IDs, status pairs, conditions). Users and agents need more context to understand the output or how to use the 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?

Schema coverage is 100% (the only parameter, storeId, is described in the schema). The description adds no additional meaning beyond the schema, so baseline 3 is appropriate. The description does not clarify whether the parameter is optional or if omitting it returns all transitions.

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 the tool's purpose: 'Get list of configured automatic Order status transitions'. It uses a specific verb ('Get') and resource ('list of configured automatic Order status transitions'), which distinguishes it from sibling tools like 'ConfigureAutomaticTransitions' that perform mutations.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., 'ConfigureAutomaticTransitions'). It does not mention typical use cases, prerequisites, or context where retrieval is appropriate.

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