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. When the user names a specific professional or practice, pass that as 'name'. Results are public profile data only. Each result includes a profileUrl that can be given to the user for booking.

Input Schema

NameRequiredDescriptionDefault
cityNoDeprecated alias for 'location', kept so agents that learned the older argument name keep working. Prefer 'location'.
nameNoName of the professional or their practice in free text, e.g. 'Müjde Koyuncu'. Every word must appear in the person's name, the practice name or the profile slug; case and accents are ignored and part of a word is enough ('koyun'). Names that start with the given words come first.
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. Changed1 schema field changed
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Name of the professional or their practice in free text, e.g. 'Müjde Koyuncu'. Every word must appear in the person's name, the practice name or the profile slug; case and accents are ignored and part of a word is enough ('koyun'). Names that start with the given words come first.",
+  "type": "string"
+}
  2. 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"
+]
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are 'public profile data only' and each result carries a profileUrl suitable for handing to the user for booking, which matters since there is no 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?

Four sentences, front-loaded with the core purpose, then scope, then the key routing hint for 'name', then output content. No wasted clauses, though the last two sentences (public data / profileUrl) could be folded together without loss.

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 9-parameter, zero-required search with no output schema, the description supplies the missing output-side context (public profile data, booking profileUrl) and the zero-filter default. What it omits is cross-tool orientation against get_provider and list_directory_filters, which the agent needs to pick correctly among the three.

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 all nine parameters are already documented with examples, enums and the deprecated-alias note. The description only reiterates the 'name' usage and the all-optional nature, adding little meaning the schema does not already carry; baseline 3 applies.

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 names a specific verb and resource ('Searches the public Vitena directory of health and wellness professionals') and even enumerates the covered disciplines, so the agent knows exactly what domain it queries. It does not explicitly distinguish itself from siblings like get_provider or list_directory_filters within the description text, so it lands at clear-but-undifferentiated.

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 concrete routing guidance ('When the user names a specific professional or practice, pass that as name') and clarifies that every filter is optional, with an unfiltered call returning the first page of everything. It never names the alternative tools to use instead (e.g. get_provider for a known entity, list_directory_filters for vocabularies), so no explicit exclusions.

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