Skip to main content
Glama

Get a print shop

get_print_shop
Read-onlyIdempotent

One print shop with its printers, materials and colors, and recent reviews.

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": {
      "shop": "<shop>"
    },
    "name": "get_print_shop"
  }
}

Input Schema

NameRequiredDescriptionDefault
shopYesThe shop id or handle from list_print_shops

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds useful payload context by naming the embedded collections (printers, materials, colors, recent reviews), which annotations cannot express. It says nothing about how many reviews are returned, pagination, or what happens if the shop id is invalid.

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 with no filler. Slight imprecision in 'recent reviews' (recency window undefined) keeps it from being ideal, but the size is appropriate for a one-parameter getter.

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?

There is no output schema, so the description must carry return-value expectations — it partially does by listing the embedded entities. It is adequate for a simple getter but leaves the review window, error behavior, and size of the embedded collections unspecified.

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 100% for the single parameter, and the schema already explains the id/handle and its origin in list_print_shops. The description adds no further meaning about the identifier, so the baseline 3 applies.

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 description names a specific resource (one print shop) and enumerates what is bundled with it (printers, materials, colors, recent reviews). It is a clear single-item getter, though it does not explicitly distinguish itself from sibling getters such as get_my_shop or get_my_store.

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?

No when-to-use guidance is given, and no alternative is named. The only routing hint — that the shop id comes from list_print_shops — lives in the input schema, not the description.

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