Skip to main content
Glama

Print Shop by Bottle Your Brand

Show a print tool

show_print_tool
Read-only

Show one of Bottle Your Brand's free artwork tools as a card the customer can open: measure-by-photo (what size sticker fits a real object), background-remover (remove a photo's background and add bleed and a cut path), cutline-generator, resolution-tester, contrast-check, size-guide, design-online. Use this instead of only mentioning a tool by name when one of them solves the problem the customer just described.

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": {
      "tool": "<tool>"
    },
    "name": "show_print_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesWhich tool to show.

Output Schema

NameRequiredDescriptionDefault
keyYes
urlYes
nameYes
when_to_useYes
preview_imageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tool / enum
      Previous value: -[
      -  "background-remover",
      -  "cutline-generator",
      -  "resolution-tester",
      -  "contrast-check",
      -  "chrome-extension",
      -  "measure-by-photo",
      -  "size-guide",
      -  "design-online"
      -]New value: +[
      +  "background-remover",
      +  "cutline-generator",
      +  "resolution-tester",
      +  "contrast-check",
      +  "measure-by-photo",
      +  "size-guide",
      +  "design-online"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly=true, destructive=false, openWorld=false, so safety is covered; the description adds UI-level behavior ('as a card the customer can open') and per-tool side effects ('add bleed and a cut path' for background-remover) that annotations do not convey. Return shape is covered by the existing output schema, so nothing critical is missing.

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?

Front-loaded with the action and resource, then the enumeration, then the usage rule — a sensible ordering with little waste. The parenthetical glosses lengthen it slightly, but each one earns its place.

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

Completeness4/5

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

A single-parameter, low-risk UI tool with a full output schema and annotations needs little more than this; the description covers what is shown and when to reach for it. The only shortfall is that half the enum values remain unexplained.

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?

Schema coverage is 100% and the enum constrains input, but the schema text is only 'Which tool to show.' The description adds real meaning for a couple of values (measure-by-photo, background-remover) while leaving cutline-generator, resolution-tester, contrast-check, size-guide and design-online as bare names.

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?

Specific verb 'Show' plus a concrete resource (one of Bottle Your Brand's free artwork tools) rendered as an openable card. The enumerated tools are each glossed (e.g. measure-by-photo = 'what size sticker fits a real object'), so an agent knows exactly what capability is being surfaced.

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

Usage Guidelines4/5

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

Explicit trigger: 'when one of them solves the problem the customer just described', and an explicit contrast against the weaker behavior of 'only mentioning a tool by name'. It stops short of routing against the sibling tools (get_sticker_guidance, upload_sticker_artwork), so there is no exclusion clause.

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