Skip to main content
Glama

My storefront

get_my_store
Read-onlyIdempotent

A seller's Printlooper storefront: its link, how many products are live, and whether Shopify is connected. product_feed_url is a public, read only list of the live products for a site the seller runs themselves: show them there and link each Buy button to the product url, where the buyer pays on Printlooper. The look, logo and about text are edited in the storefront editor on Printlooper. 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_store"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: product_feed_url is a public read-only list of live products, buyers pay on Printlooper rather than at the linked site, and look/logo/about text must be changed in the storefront editor instead of here. That last point usefully signals this tool cannot perform edits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The what-you-get summary is front-loaded, which is good, but the middle sentence mixes rendering instructions for Buy buttons with field semantics and runs long. Parts of it read as UI guidance rather than tool definition, adding bulk without sharpening when or how to invoke the call.

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 explaining returns and does so for the key fields, plus it states the account prerequisite and the read-only nature of the feed. It stops short of describing the shape or null-handling of the Shopify-connected indicator, but an agent has enough to call it and interpret the result.

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?

The tool takes zero parameters, so the schema baseline is 4; however, the description's field-level detail (link, live product count, Shopify status, product_feed_url) describes return values rather than parameters. It is helpful orientation but not parameter semantics, so it sits slightly below the zero-param baseline.

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 first sentence names the specific resource (a seller's Printlooper storefront) and enumerates what it surfaces: the link, live product count, and Shopify connection status. That is a concrete verb+resource statement rather than a restatement of the name. It does not explicitly distinguish itself from the similarly named sibling get_my_shop, leaving some ambiguity about storefront vs. shop.

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?

It gives one real prerequisite ("Needs a connected Printlooper account") and implies usage through the Buy-button rendering guidance, but never states when to call this versus get_my_shop, get_my_account, or get_my_listings. The when-to-use context is implied rather than 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