Skip to main content
Glama

SzuruSzuru – rezerwacja czyszczenia tapicerki

by pl.szuruszuru
OverviewDiscussionsAdmin

Lista usług SzuruSzuru

list_upholstery_services
Read-onlyIdempotent

PURPOSE: Lists SzuruSzuru services (mobile upholstery, corner sofa, armchair, carpet, rug and mattress cleaning at the customer's home, Pomeranian region, Poland) with service ids, unit prices in PLN, units and add-on names. WHEN TO USE: To find the service id and exact add-on names before calculate_quote, or when the customer asks what is offered. WHEN NOT TO USE: Not for a price of a concrete order (use calculate_quote), not for coverage (check_service_area) or dates (check_availability). REQUIRED: nothing. SIDE EFFECTS: none (read-only). CONSTRAINTS: Prices come only from this catalog and calculate_quote - never estimate a price.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoOptional filter (furniture = sofas, corner sofas, armchairs; leather = leather furniture)
session_idNoOptional, ignored by this tool.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNo
errorNoStable machine-readable error id when success=false, e.g. missing_required_fields, unsupported_postcode, no_availability
messageNo
successYestrue = operation done / data returned; false = see error
servicesNo
session_idNo
pricing_rulesNo
missing_fieldsNo
catalog_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Optional filter (leather = leather furniture)"New value: +"Optional filter (furniture = sofas, corner sofas, armchairs; leather = leather furniture)"
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Optional, ignored by this tool.",
+  "maxLength": 40,
+  "minLength": 28,
+  "pattern": "^as_[0-9a-z]{26}$",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "catalog_version": {
+      "type": "string"
+    },
+    "code": {
+      "type": "string"
+    },
+    "error": {
+      "description": "Stable machine-readable error id when success=false, e.g. missing_required_fields, unsupported_postcode, no_availability",
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "missing_fields": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "pricing_rules": {
+      "type": "object"
+    },
+    "services": {
+      "items": {
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "name_pl": {
+            "type": "string"
+          },
+          "unit": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "session_id": {
+      "type": "string"
+    },
+    "success": {
+      "description": "true = operation done / data returned; false = see error",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is largely pre-declared. The description nonetheless adds a useful domain constraint not present in structured data: prices come only from this catalog and calculate_quote, never estimated. It does not add much beyond that (no pagination or ordering behavior), so it sits just above adequate.

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?

Labeled sections (PURPOSE / WHEN TO USE / WHEN NOT TO USE / REQUIRED / SIDE EFFECTS / CONSTRAINTS) make it scannable, and the purpose is front-loaded before the routing rules. Every sentence carries a distinct instruction; no filler.

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?

Output schema exists, so return-value explanation is unnecessary, yet the description still names the key returned fields. Required params (none), side effects, filtering option and the pricing constraint are all covered, leaving no gap for an agent to call it correctly.

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 both parameters (category enum with its meaning, session_id being ignored) are fully documented in the schema. The description adds no parameter syntax or format detail beyond that, so the baseline 3 is correct.

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?

States a specific verb (Lists) and resource (SzuruSzuru services) with scope: the service domain, region, and the exact fields returned (service ids, unit prices in PLN, units, add-on names). An agent can distinguish it from calculate_quote and the other siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit WHEN TO USE (find service id / exact add-on names before calculate_quote, or answer what is offered) and WHEN NOT TO USE with named alternatives for each excluded case (calculate_quote for order pricing, check_service_area for coverage, check_availability for dates). Nothing is left to inference.

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

All SzuruSzuru – rezerwacja czyszczenia tapicerki 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