Skip to main content
Glama
Sign In
E-Nabız MCP

E-Nabız MCP

by UmutKDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

enabiz_list_appointments

Read-only

Retrieve your upcoming E-Nabız appointments including date, clinic, and physician. Filter by appointment status.

Instructions

E-Nabız (MHRS) randevularını listeler — salt-okunur.

Sayfada gösterilen randevuları döndürür (tarih/saat, kurum, klinik, muayene yeri, hekim, durum, tür). status_query verilirse durum alanında büyük/küçük harf duyarsız filtre uygular. Randevu almaz/iptal etmez. Kimlikli oturum gerektirir; yoksa error: "auth_required".

  • limit: en fazla kaç kayıt döner (varsayılan 50; 0 = sınırsız). truncated: true ise liste kırpılmıştır.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "enabiz_list_appointments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
status_queryNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds that it returns only displayed appointments, details limit behavior with truncated flag, and explicitly states no mutation. No contradiction with annotations.

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?

The description is concise, front-loading the purpose, then adding parameter details and constraints. Every sentence is informative without redundancy.

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?

Given the presence of an output schema, the description adequately covers parameter behavior, auth requirements, and the read-only constraint. It could mention error handling beyond auth_required, but overall sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description thoroughly explains both parameters: limit's default and behavior, and status_query's case-insensitive filtering. This fully compensates for the lack of schema descriptions.

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 clearly states the tool lists E-Nabız appointments, specifies it is read-only, and lists the fields returned. It distinguishes from siblings by focusing on appointments, with a specific verb and resource.

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 explains it does not take/cancel appointments and requires an authenticated session. However, it does not explicitly contrast with sibling tools or provide when-not-to-use guidance beyond the read-only nature.

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

Deploy Server

Other Tools