Skip to main content
Glama

SzuruSzuru – rezerwacja czyszczenia tapicerki

by pl.szuruszuru
OverviewDiscussionsAdmin

Sprawdź obszar

check_service_area
Read-onlyIdempotent

PURPOSE: Checks whether SzuruSzuru serves a Polish postal code. WHEN TO USE: When the customer asks whether we come to their town/postal code. WHEN NOT TO USE: Not needed before calculate_quote (calculate_quote checks the area itself). Never use it to reserve anything. REQUIRED: postal_code (NN-NNN). SIDE EFFECTS: none (read-only). RESULT: served -> success=true, available=true, city. Not served -> success=false, error="unsupported_postcode", available=false - tell the customer we do not serve this code; do not continue to quote or booking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idNoOptional, ignored by this tool.
postal_codeYesPolish postal code NN-NNN, e.g. 80-180

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo
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
postcodeNo
availableNo
session_idNo
postal_codeNo
missing_fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / postal_code / description
      Added value: +"Polish postal code NN-NNN, e.g. 80-180"
    • changedInput schema / properties / postal_code / pattern
      Previous value: -"^\\d{2}-?\\d{3}$"New value: +"^\\d{2}[-\\s]?\\d{3}$"
    • 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": {
+    "available": {
+      "type": "boolean"
+    },
+    "city": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "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"
+    },
+    "postal_code": {
+      "type": "string"
+    },
+    "postcode": {
+      "type": "string"
+    },
+    "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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so 'SIDE EFFECTS: none' is partly redundant. What the description adds beyond structured data is the failure path — success=false, error='unsupported_postcode', available=false — plus the directive to stop the customer at that point rather than continue to quote or booking. That is genuine behavioral guidance, though it overlaps with the existing 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?

The labeled PUrpose/WHEN/REQUIRED/RESULT structure is front-loaded and scannable, and each block earns its place. Minor redundancy: 'SIDE EFFECTS: none (read-only)' duplicates the annotations, and 'REQUIRED: postal_code' duplicates the schema.

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?

For a single-parameter eligibility check with an output schema, annotations, and a named sibling, nothing an agent needs is missing: input format, exclusions, expected result shape, and the escalation rule on failure are all present.

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%, and the schema already documents the NN-NNN pattern with an example and notes that session_id is ignored. The description's 'REQUIRED: postal_code (NN-NNN)' restates the schema without adding format, validation, or edge-case meaning, so the baseline 3 applies.

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 opens with a precise verb and resource: 'Checks whether SzuruSzuru serves a Polish postal code.' It names the sibling calculate_quote explicitly, so an agent can separate this read-only eligibility check from the quoting tool without inspecting either 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?

It gives explicit WHEN TO USE ('when the customer asks whether we come to their town/postal code') and WHEN NOT TO USE ('not needed before calculate_quote — calculate_quote checks the area itself', 'never use it to reserve anything'). The alternative tool and the condition selecting it are spelled out, not inferred.

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