Skip to main content
Glama

Shop overview

get_shop_overview
Read-onlyIdempotent

Facts about LivaGlow and its single product, the personalised ceramic mug: specs, fixed prices, volume discount, shipping (Germany only), delivery, returns policy, photo requirements and key URLs. For a quote use calculate_price, for delivery dates use get_delivery_estimate.

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_shop_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower, and the description still adds real context: prices are 'fixed' (not dynamically computed), shipping is 'Germany only', and the payload is a static set of reference facts rather than a parameterised query. It does not state the return format, but for a zero-argument lookup that is a minor omission.

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: the first front-loads the resource and its full content inventory, the second routes to alternatives. Every clause earns its place, with no filler or restatement of the title.

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

Completeness5/5

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

For a static, zero-argument reference tool with no output schema, the description is complete: it tells the agent what topics are covered so it knows whether calling is worthwhile, and it handles the cross-shopping cases where a sibling is the better call. Nothing needed to invoke it correctly is missing.

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 semantics to explain and the baseline of 4 applies. The description correctly implies a parameterless facts lookup rather than hinting at any filtering input the schema cannot accept.

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?

The description names the specific resource (LivaGlow's shop and its single ceramic mug product) and enumerates exactly what facts it returns: specs, fixed prices, volume discount, shipping, delivery, returns, photo requirements, URLs. It also explicitly distinguishes itself from the quoting and delivery-date siblings by name, so an agent can select it without opening a schema.

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?

It gives concrete routing rules: 'For a quote use calculate_price, for delivery dates use get_delivery_estimate.' That is clear when-to-use guidance for two ambiguous neighbours. It stops short of addressing overlaps with other siblings such as get_care_and_safety, get_design_options, or search_faq, whose scopes could plausibly intersect with 'specs' or 'photo requirements.'

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