SzuruSzuru – rezerwacja czyszczenia tapicerki

Wymagania usługi

get_service_requirements

Read-onlyIdempotent

PURPOSE: Returns the details of ONE service: unit (piece / m2 / mattress side), allowed quantity, add-on names and prices, short description and FAQ. WHEN TO USE: When the request is ambiguous (e.g. which corner sofa size, carpet area in m2, which add-ons exist for this service). WHEN NOT TO USE: Not for prices of an order (use calculate_quote) or availability. REQUIRED: service (id from list_upholstery_services). SIDE EFFECTS: none (read-only).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`service`	Yes	Service id from list_upholstery_services, e.g. pranie_naroznika_l_4_5_os
`session_id`	No	Optional, ignored by this tool.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`code`	No
`unit`	No
`error`	No	Stable machine-readable error id when success=false, e.g. missing_required_fields, unsupported_postcode, no_availability
`message`	No
`name_pl`	No
`success`	Yes	true = operation done / data returned; false = see error
`session_id`	No
`price_model`	No
`missing_fields`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 1, 2026

changedInput schema / properties / service / description

Previous value: -"Service id from list_upholstery_services"New value: +"Service id from list_upholstery_services, e.g. pranie_naroznika_l_4_5_os"

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": {
+    "code": {
+      "type": "string"
+    },
+    "error": {
+      "description": "Stable machine-readable error id when success=false, e.g. missing_required_fields, unsupported_postcode, no_availability",
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "missing_fields": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "name_pl": {
+      "type": "string"
+    },
+    "price_model": {
+      "type": "object"
+    },
+    "session_id": {
+      "type": "string"
+    },
+    "success": {
+      "description": "true = operation done / data returned; false = see error",
+      "type": "boolean"
+    },
+    "unit": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

First observedSep 20, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data; the description's 'SIDE EFFECTS: none (read-only)' largely restates it. It does add value by disclosing the breadth of returned content, but that overlaps the output schema.

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?

Labelled sections (PURPOSE / WHEN TO USE / WHEN NOT TO USE / REQUIRED / SIDE EFFECTS) make it scannable and front-loaded. One clause, the side-effects note, duplicates the annotations rather than adding new information.

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?

Given an output schema is present, the description need not detail return values, and it still supplies purpose, routing conditions, the required parameter source, and a safety note. An agent has everything needed to select and invoke 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 the service id and the ignored session_id are already documented in the schema exactly as the description repeats them. Baseline 3 is correct when the schema carries the full parameter burden.

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 states a specific verb and resource ('Returns the details of ONE service') and enumerates exactly what is returned (unit, quantity, add-ons, description, FAQ). This lets an agent distinguish it from siblings like list_upholstery_services or calculate_quote 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 ('when the request is ambiguous') and WHEN NOT TO USE ('not for prices of an order (use calculate_quote) or availability') sections name both the condition and the alternative sibling tools. 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 tools Inspect

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

Need Help?