Skip to main content
Glama

My print shop

get_my_shop
Read-onlyIdempotent

Your print shop: name, approval, capacity, daily order cap, lead time, every material with its prices and colors, and how many products of its own it sells (list them with list_my_products). 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": "get_my_shop"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered structurally. The description adds value beyond that by stating the account-connection prerequisite, which is the main failure mode for this call, though it says nothing about error behavior when no shop is connected.

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?

A single front-loaded sentence where the returned-field enumeration and the sibling cross-reference both carry information. The parenthetical routing note is slightly cramped inside a long list, but nothing is redundant.

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?

With no output schema, the description carries the burden of describing returns and does so field by field, plus the account prerequisite. The only meaningful gap is the unresolved ambiguity against the sibling get_print_shop.

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 takes zero parameters, so there is no parameter surface to document and the baseline of 4 applies. The description correctly does not waste space on arguments.

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?

Names the resource concretely ('Your print shop') and enumerates exactly what it returns: name, approval, capacity, daily order cap, lead time, materials with prices and colors, and product count. The possessive framing distinguishes it from a generic shop lookup, but the description never explicitly contrasts it with the sibling get_print_shop, so an agent must infer the difference.

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?

Gives a real precondition ('Needs a connected Printlooper account') and routes product listing to the correct sibling: 'list them with list_my_products'. No explicit when-not-to-use guidance or contrast with get_print_shop, so it falls short of a 5.

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