Skip to main content
Glama

Sanovia — medici e professionisti sanitari in Italia

by app.sanovia
OverviewDiscussionsAdmin

Cerca professionisti / Search practitioners

search_doctors
Read-onlyIdempotent

Cerca medici e professionisti sanitari italiani iscritti a Sanovia per specialità e/o città. Elenca solo chi ha la pagina di prenotazione online e un sito pubblicato: il proprio, oppure quello della struttura (poliambulatorio, centro) in cui riceve — in quel caso site_url è il sito della struttura. Non prenota: restituisce il link di prenotazione. / Search Italian doctors and health practitioners on Sanovia by specialty and/or city. Lists only practitioners with an online booking page and a published website: their own, or that of the structure (clinic) they practise in — then site_url is the structure's site. Does not book; returns the booking link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCittà della sede, es. «Bologna». / City of the practice.
limitNoMassimo risultati (default 10, max 20). / Max results.
specialtyNoSpecialità o professione, in italiano: la disciplina («Cardiologia», «Odontoiatria», «Medicina Generale», «Fisioterapia», «Osteopatia») oppure il professionista («cardiologo», «dentista», «medico di base», «fisioterapista», «osteopata»). / Specialty or profession, in Italian: the discipline (e.g. «Cardiologia») or the practitioner noun (e.g. «cardiologo»).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
doctorsYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / specialty / description
      Previous value: -"Specialità o professione, es. «cardiologo», «fisioterapista». / Specialty or profession."New value: +"Specialità o professione, in italiano: la disciplina («Cardiologia», «Odontoiatria», «Medicina Generale», «Fisioterapia», «Osteopatia») oppure il professionista («cardiologo», «dentista», «medico di base», «fisioterapista», «osteopata»). / Specialty or profession, in Italian: the discipline (e.g. «Cardiologia») or the practitioner noun (e.g. «cardiologo»)."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "doctors": {
+      "items": {
+        "properties": {
+          "booking_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "cities": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "code": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "online_booking": {
+            "type": "boolean"
+          },
+          "practice_name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "profession_types": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "site_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "specialty": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "code",
+          "name",
+          "specialty",
+          "practice_name",
+          "profession_types",
+          "online_booking",
+          "booking_url",
+          "site_url",
+          "cities"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "doctors",
+    "truncated"
+  ],
+  "type": "object"
+}
  3. 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 readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description still adds real value beyond that: entries are constrained to practitioners with a live booking page and published site, site_url may actually point to the clinic rather than the practitioner, and the tool returns a booking link rather than booking. This is meaningful behavioral context, though rate limits/caching are unmentioned.

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 scoping and non-booking constraint are front-loaded and each sentence earns its place. The cost is full bilingual duplication, which is redundant for a single-language agent consumer, so it is efficient but not maximally tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering the safety profile, the description does not need to explain return values, and it already clarifies the notable site_url semantics and the listing constraint. It is essentially complete for calling the tool correctly; only the absence of sibling routing leaves a small gap.

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 all three parameters (city, specialty, limit) are documented inline with examples and constraints. The description only restates the specialty-and-city filtering, adding no syntax or behavior beyond the schema, 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 names a specific verb (search/list) and resource (Italian doctors and health practitioners on Sanovia) and bounds the scope to specialty and/or city. It also disambiguates against siblings like get_availability and get_doctor_profile by stating it does not book and only returns a booking link, and it specifies the inclusion filter (only practitioners with a booking page and published website).

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?

It gives clear when-to-use context: find practitioners filtered by specialty and/or city, and explicitly notes it does not perform bookings. However, it never names the sibling alternatives (get_doctor_profile, get_availability) or states when a caller should prefer them, so the routing guidance stops short of explicit exclusions.

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