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

E-Nabız MCP

by UmutKDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

enabiz_list_device_prescriptions

Read-only

Lists medical device prescriptions from E-Nabız by year range. Optionally filters by facility name and limits results.

Instructions

E-Nabız tıbbi cihaz reçetelerini yıl aralığına göre listeler.

  • start_year / end_year: yıl aralığı. Verilmezse son 6 takvim yılı (bu yıl - 5 … bu yıl).

  • facility_query: verilirse TESİS bilgisinde büyük/küçük harf duyarsız filtre.

Her reçete tarih, reçete no, hekim ve tesis bilgisi ile döner. 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_device_prescriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
end_yearNo
start_yearNo
facility_queryNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, openWorldHint), the description details auth requirements, default year range, case-insensitive facility filtering, pagination with limit and truncation flag. No contradictions.

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?

Description is well-structured with bullet points, front-loaded with main purpose, every sentence adds necessary detail without redundancy.

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

Completeness5/5

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

Given 4 optional parameters, output schema exists, annotations present, the description covers all behavioral aspects: auth, default ranges, filtering, pagination, and returned fields. Complete.

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?

Schema coverage is 0%, so description fully explains parameters: start_year/end_year default to last 6 years, facility_query is case-insensitive filter, limit default 50 with 0 meaning unlimited and truncated flag. Adds significant value.

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 medical device prescriptions by year range. The name distinguishes it from sibling tools like enabiz_list_prescriptions and enabiz_list_optical_prescriptions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains parameters and defaults but does not explicitly state when to use this tool versus alternatives. It implies use for device prescriptions but lacks explicit when-not or sibling differentiation.

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