Skip to main content
Glama
Sign In
Superzoo MCP

Superzoo MCP

by benjaminstary
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

get_product

Read-onlyIdempotent

Retrieve product details, variants, public EUR offers in Slovakia, delivery availability, and store count to check pricing and availability.

Instructions

Get product details, variants, public online EUR offers in Slovakia, delivery availability and available-store count. Price variant identifies conditional offers such as familyPrice; membership eligibility and branch prices are not verified.

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": {
      "product_id": "<product_id>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful behavioral context not in the annotations: results are limited to public online EUR offers in Slovakia, and membership/branch pricing is explicitly unverified. It stops short of noting pagination, offer freshness, or empty-result behavior.

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?

Two tight sentences with the payload scope front-loaded and the trust caveat placed after it. The phrase "Price variant identifies conditional offers such as familyPrice" is compressed to near-cryptic, but nothing is padded.

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?

With no output schema, the description must carry the return shape, and it does enumerate the returned elements adequately. However, for an open-world read tool keyed on an opaque ID, missing guidance on where product_id comes from and what an empty/not-found response looks like leaves a real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single product_id parameter carries only a regex pattern, not prose. The description says nothing about the identifier's origin or format, so it does not compensate for the coverage gap at all.

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?

Opens with a specific verb+resource ("Get product details") and enumerates the payload scope: variants, public online EUR offers in Slovakia, delivery availability, store count. It is clear what the tool returns, but it never distinguishes itself from the sibling get_product_availability, which the availability wording overlaps with.

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 statement of when to use this versus search_products or get_product_availability, and no prerequisites (e.g. obtaining a product_id). The caveat about membership eligibility and branch prices is a data-trust note, not usage routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools