Skip to main content
Glama

get_shop_details

Read-onlyIdempotent

Get a shop profile: description, locations, rating, main brands and categories. Identify the shop with shop_id (from search_shops), slug, or shop_name.

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

Input Schema

NameRequiredDescriptionDefault
slugNoShop slug in the form {id}-{text}, as used in the source URL.
shop_idNoShop id returned by search_shops.
languageNoOptional language code.
shop_nameNoShop name, used when no id or slug is known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety and repeatability are covered there. The description adds useful context about what the response contains and how the shop is targeted, but says nothing about not-found behavior or how the optional language affects returned text.

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 tight sentences with zero filler; the returned-fields summary is front-loaded and the identifier guidance follows immediately. Nothing repeats the tool name or pads the text.

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?

For a simple all-optional lookup with no output schema, the description covers both what is returned and how to select the target shop, which is what an agent needs to call it. The only gap is edge-case behavior such as missing or ambiguous shops.

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%, so all four parameters are already documented, including the slug format and that shop_name is a fallback. The description largely restates those semantics rather than adding new meaning, so the baseline of 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?

Uses a specific verb ('Get') and resource ('shop profile') and enumerates the returned fields (description, locations, rating, main brands, categories), which lets an agent distinguish it from search_shops or get_brand_details. It stops short of explicitly contrasting itself with the closest sibling, but the resource is unambiguous.

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 concrete lookup guidance by naming the three acceptable identifiers and flagging that shop_id originates from search_shops, implying a resolution order (id, then slug, then name). It does not state exclusions or what to do when a shop is not found, so it falls short of full when/when-not guidance.

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