Skip to main content
Glama

Pause or limit new orders

set_shop_capacity
Destructive

Pause new orders (your pending orders are rerouted to other shops and your sellers are told), resume them, or change your daily order cap. Needs a connected Printlooper account.

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

Input Schema

NameRequiredDescriptionDefault
pausedNo
daily_order_capNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds genuinely useful consequence detail beyond them: pending orders are rerouted to other shops and sellers are notified. It also discloses the prerequisite of a connected Printlooper account. It stops short of saying whether pausing affects in-flight orders or whether the change is reversible.

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, front-loaded with the actions and their operational consequence, followed by the prerequisite. No filler or repetition.

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?

The description covers the key side effect and auth prerequisite for a destructive mutation with no output schema, which is the important part. However, with 0% schema coverage and zero required parameters, it leaves unresolved how the two optional parameters combine and what a call with no arguments accomplishes.

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 0%, so the description must carry parameter meaning. It maps the options to the two parameters only loosely (pause/resume implying the boolean, cap implying the integer) without stating that resume means setting paused to false, or what an empty call does given zero required parameters.

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?

Names three concrete operations on a specific resource (pause new orders, resume them, change the daily order cap) and describes the shop-wide effect of rerouting pending orders, which separates this from per-listing tools. An agent can tell what it does without opening the schema.

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 implies the three modes but never states when to prefer pausing versus lowering the cap, nor what happens when the tool is called with no parameters (all params are optional). Guidance is inferable from the option names but not explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources