Skip to main content
Glama

Vitena Directory

by care.vitena
OverviewDiscussionsAdmin

Search health professionals

search_providers
Read-onlyIdempotent

Searches the public Vitena directory of health and wellness professionals who accept appointments (dietitians, dentists, physiotherapists, psychologists, beauty and aesthetics practitioners, child development specialists). Every filter is optional; with no filters it returns the first page of all publicly listed professionals. Results are public profile data only. Each result includes a profileUrl that can be given to the user for booking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoDeprecated alias for 'location', kept so agents that learned the older argument name keep working. Prefer 'location'.
pageNo1-based page number. Page size is fixed at 20.
countryNoTwo-letter ISO country code, e.g. 'TR', 'ES', 'DE'. Narrows an ambiguous place name. Valid values come from 'countries' in list_directory_filters.
languageNoTwo-letter language code the professional consults in, e.g. 'es', 'tr'.
locationNoCity, district or region name in free text, e.g. 'Istanbul', 'Kadıköy', 'Madrid', 'Andalucía'. Resolved against a place gazetteer, so it does NOT have to match a fixed list and is NOT returned by list_directory_filters — pass the place the user actually named. Choosing a region matches everywhere inside it. An unrecognised place returns an explanatory error rather than silently ignoring the filter.
workModeNoConsultation mode. 'online' for remote, 'in_person' for on-site.
disciplineNoProfession to filter by. One of: dietitian, psychologist, physiotherapist, beauty, child-development, dentist, doctor, other.
specializationNoSpecialization CODE (not label) as returned by list_directory_filters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / discipline / description
      Previous value: -"Profession to filter by. One of: dietitian, psychologist, physiotherapist, beauty, child-development, dentist, other."New value: +"Profession to filter by. One of: dietitian, psychologist, physiotherapist, beauty, child-development, dentist, doctor, other."
    • changedInput schema / properties / discipline / enum
      Previous value: -[
-  "dietitian",
-  "psychologist",
-  "physiotherapist",
-  "beauty",
-  "child-development",
-  "dentist",
-  "other"
-]New value: +[
+  "dietitian",
+  "psychologist",
+  "physiotherapist",
+  "beauty",
+  "child-development",
+  "dentist",
+  "doctor",
+  "other"
+]
  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, idempotentHint, and destructiveHint, so the description only needs to add context. It adds that results are public profile data only assimilation, that professionals accept appointments, and that each result includes a profileUrl for booking – useful behavioral detail beyond the annotations.

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 description is well front-loaded with the core search purpose and includes only relevant clauses. The discipline enumeration partly duplicates the schema enum, so a small amount of redundancy prevents a perfect score.

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?

For a tool with zero required parameters and rich annotations, the description covers the essential output insight (profileUrl) and default behavior. It could more explicitly point to list_directory_filters for filter values and to get_provider for single-provider details, but those are already partially implied/introduced in the schema.

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 baseline is 3. The description confirms that all filters are optional and that no filters returns the first page, but it does not add per-parameter syntax or format details beyond what the schema already provides.

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 action ('Searches the public Vitena directory') and resource (health and wellness professionals who accept appointments), and lists example disciplines. The verb 'search' differentiates it from get_provider (single record) and list_directory_filters (filter metadata) even without naming them.

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?

Provides clear context: every filter is optionalable, no filters returns the first page, and results are public profile data with a usable profileUrl. It does not explicitly name when to prefer get_provider or list_directory_filters, but the search-and-return-profile-Url flow is well implied.

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

All Vitena Directory 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