Skip to main content
Glama

TATUAT.RO — Tattoo & Piercing Supplies

by io.github.estartoken
OverviewDiscussionsAdmin

Fișa unui produs de pe tatuat.ro

get_product
Read-onlyIdempotent

Întoarce fișa completă a unui produs de pe tatuat.ro după slug: nume, descriere, preț efectiv în RON (cu prețul dinainte de reducere dacă e cazul), disponibilitate, link direct la fișă, brand și variantele cu preț și stoc propriu. Folosește slug-ul întors de search_products. Dacă slug-ul nu corespunde unui produs activ, found este false — nu e o eroare.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSlug-ul produsului, exact cel întors de search_products sau cel din URL-ul fișei (ex. „ace-cartus-0-30-rl"), fără prefixul /product/.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
foundYesDacă slug-ul corespunde unui produs activ pe tatuat.ro. false ≠ eroare.
productYesFișa produsului, sau null dacă slug-ul nu corespunde niciunui produs activ.
order_restrictionYesRestricția de comandă a produsului, sau null dacă n-are niciuna (și la found: false). hu_only = se poate comanda DOAR cu livrare în Ungaria; o comandă cu livrare în România va fi refuzată la plasare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / order_restriction
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "hu_only"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Restricția de comandă a produsului, sau null dacă n-are niciuna (și la found: false). hu_only = se poate comanda DOAR cu livrare în Ungaria; o comandă cu livrare în România va fi refuzată la plasare."
+}
    • changedOutput schema / required
      Previous value: -[
-  "found",
-  "product"
-]New value: +[
+  "found",
+  "product",
+  "order_restriction"
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the found=false-not-an-error contract and the fact that prices include pre-discount context and per-variant stock.

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 sentences, front-loaded with the return scope followed by usage and edge-case handling; no filler. The field enumeration is dense but each item maps to real output, so it earns its place.

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?

An output schema exists, so return values need not be spelled out, yet the description still names the key fields and covers the slug-provenance and not-found semantics. Nothing an agent needs to call this correctly is missing.

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 coverage is 100% and the single parameter's format (slug from search_products or the /product/ URL, without prefix) is already documented in the schema. The description only reinforces the same source hint, adding little beyond it – baseline 3.

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?

Specific verb+resource ('Întoarce fișa completă a unui produs de pe tatuat.ro după slug') plus an enumeration of the returned fields (nume, descriere, preț în RON, disponibilitate, link, brand, variante). It also implicitly differentiates itself from search_products by consuming its output.

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?

Explicitly tells the agent where the argument comes from ('Folosește slug-ul întors de search_products') and defines the non-error branch when the slug doesn't match an active product. It gives no exclusion against siblings like get_stock or browse_category, so it stops short of a 5.

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

All TATUAT.RO — Tattoo & Piercing Supplies toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources