Skip to main content
Glama
UmutKDev

E-Nabız MCP

by UmutKDev
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

enabiz_list_medications

Read-only

Lists prescribed medications from your health records by year range, with optional drug name filter. Returns prescription date, drug name, dosage, quantity, hospital, and clinic.

Instructions

E-Nabız kullanılan ilaçları 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).

  • drug_query: verilirse ilaç adında büyük/küçük harf duyarsız filtre.

Her ilaç reçete tarihi, barkod, ad, doz, periyot, kullanım, kutu adedi, hastane ve klinik 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
end_yearNo
drug_queryNo
start_yearNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Discloses authentication requirement and truncation behavior beyond annotations; adds value without contradicting readOnlyHint.

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?

Well-structured bullet points, concise yet complete, no wasted sentences.

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?

Covers year range, filter, limit, authentication, truncation; output schema handles return values.

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?

All 4 parameters fully described with defaults and behavior, compensating for 0% schema coverage.

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?

Clearly states it lists medications by year range, distinguishing it from sibling list tools for other health data.

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?

Specifies when to use (list medications by year range) and how to filter; could improve by explicitly contrasting with siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/UmutKDev/e-nabiz-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server