Skip to main content
Glama

Sanovia — medici e professionisti sanitari in Italia

by app.sanovia
OverviewDiscussionsAdmin

Orari liberi / Free time slots

get_availability
Read-onlyIdempotent

Orari di inizio liberi per la prenotazione online di un professionista, giorno per giorno (massimo 14 giorni). Mostra solo gli orari liberi, mai chi ha prenotato. Non prenota: per prenotare il paziente usa booking_url. / Free start times for online booking, day by day (max 14 days). Shows free times only, never who booked. Does not book: the patient books at booking_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesCodice pubblico del medico restituito da search_doctors (campo `code`). / The doctor's public code from search_doctors (`code`).
daysNoNumero di giorni (default 7, max 14). / Number of days.
fromNoPrimo giorno AAAA-MM-GG (default oggi, fuso Europe/Rome). / First day YYYY-MM-DD (default today, Europe/Rome).
location_refNoOpzionale: numero della sede (location_ref) da get_doctor_profile. Senza, la sede principale. / Optional location number (location_ref) from get_doctor_profile; defaults to the primary location.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysYes
fromYes
locationYes
free_slotsYes
booking_urlYes
other_locationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "booking_url": {
+      "type": "string"
+    },
+    "days": {
+      "type": "number"
+    },
+    "free_slots": {
+      "items": {
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "slots": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "date",
+          "slots"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "from": {
+      "type": "string"
+    },
+    "location": {
+      "properties": {
+        "city": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "location_ref": {
+          "type": "number"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "location_ref",
+        "name",
+        "city"
+      ],
+      "type": "object"
+    },
+    "other_locations": {
+      "items": {
+        "properties": {
+          "city": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "location_ref": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "location_ref",
+          "name",
+          "city"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "location",
+    "other_locations",
+    "from",
+    "days",
+    "free_slots",
+    "booking_url"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the tool's safety profile is covered. The description adds the meaningful privacy context that it 'never shows who booked' and explicitly clarifies it does not perform booking. This goes beyond the annotations but doesn't add much more behavioral detail like timezone or pagination behavior, though those are partly covered by the schema.

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?

Three short, information-dense sentences in both languages, with the core purpose front-loaded first. Each sentence earns its place: it states the resource, clarifies the privacy boundary, and routes booking to booking_url. There is no filler or unnecessary detail.

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?

The tool has no missing context for an agent to use it correctly: the purpose is clear, the parameter schema is fully described, annotations declare read-only/idempotent behavior, and an output schema exists so return values don't need explanation. The only routing hint, booking_url, is included, and the boundary against showing private booking data is explicitly stated.

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 the parameters are already fully documented with types, defaults, and constraints. The description's mention of 'max 14 days' repeats the schema's days maximum and adds no new parameter semantics. Therefore, the baseline of 3 is appropriate.

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?

The description clearly states the resource: free start times for online booking, day by day, with a 14-day limit. It also adds a negative boundary ('never who booked', 'does not book') that prevents confusion with a booking action. It does not explicitly name sibling tools (get_doctor_profile, get_visit_types, search_doctors), but the resource is distinct enough to make purpose unambiguous.

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?

The description gives a clear context ('free start times for online booking') and explicitly says that booking must happen at booking_url, so the agent knows not to use this tool for booking. However, it does not explicitly distinguish this tool from the sibling tools such as get_visit_types, leaving that differentiation implied rather than stated.

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

All Sanovia — medici e professionisti sanitari in Italia 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