Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EXIRYAB_MCP_PROXYNoHTTP proxy for every request, e.g. http://user:pass@host:port
EXIRYAB_MCP_BASE_URLNoAPI base URL, e.g. a local ExirYab for developmenthttps://exiryab.com

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
ey_search_doctorsA

Find an Iranian doctor on exiryab.com by name, city and/or specialty: the best match plus alternatives, each with profile URL, clinics, phones, working hours and map links.

Give at least one of name, city, specialty (Persian works best). With a name, the server ranks by how well the name matches and drops filters that leave no match (see understood.dropped_filters and warnings). Without a name, it returns the top-ranked doctors for the city and specialty.

confidence: high = one clear match for the name; medium = a good match but others are close, so confirm with the user; low = only weak name matches; ranking = no name was given; none = nothing found. match.kind per doctor: name, partial_name, similar (padding: same specialty and area, not the name asked for) or ranking. Clinic weekly_hours maps an English day to its shifts ('17:00-19:00'); an empty list means closed that day.

ey_citiesA

Cities that have doctors on exiryab.com, with their province and doctor count, most doctors first.

Use it to find the exact Persian city name for ey_search_doctors(city=...), or to check whether a town is covered. total counts every match, not only the ones returned.

ey_specialtiesA

Medical specialties on exiryab.com with their doctor count, most doctors first; sub-specialties name their parent.

Use it to turn a word like 'قلب' or 'پوست' into the exact specialty for ey_search_doctors(specialty=...) when the user's word is ambiguous (heart: «قلب و عروق» cardiology or «جراح قلب» heart surgery).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct role: ey_search_doctors performs the actual lookup, while ey_cities and ey_specialties are enumerations that feed exact filter values into the search. The descriptions explicitly cross-reference this relationship, leaving no realistic chance of misselection.

Naming Consistency4/5

All tools share a consistent `ey_` prefix and snake_case, with clear domain-oriented names. The only minor deviation is that one is verb-led (search_doctors) while the other two are noun-only (cities, specialties), which is natural for enumeration vs action but slightly breaks a single pattern.

Tool Count4/5

Three tools is lean but well-motivated: a rich search endpoint plus two small lookup vocabularies. Nothing feels redundant, though the surface is thin enough that a single additional tool (e.g. fetch doctor by URL) could be justified.

Completeness4/5

The search tool already returns profiles, clinics, phones, hours and map links, and the two enumerations cover the full filter vocabulary, so the core directory workflow is closed. A direct profile-by-URL/ID retrieval and any booking/contact operations are absent, but reasonable workarounds exist.

Maintenance

ActivityMaintained
ResponsivenessNo issues