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

E-Nabız MCP

by UmutKDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

enabiz_list_allergies

Read-only

Retrieve allergy records from your E-Nabız health data, including drug, diagnosis, and skin test allergies. Filter results by category and set a limit.

Instructions

E-Nabız alerji kayıtlarını listeler — salt-okunur.

Üç kategoriyi birleştirir: ilac (ilaç alerjileri), tani (tanı bazlı), deri (deri/prick testleri). Her kayıt tarih, kategori, alerji türü, ilaç adı ve belirtileri ile döner. category verilirse yalnız o kategori 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_allergies"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds value by explaining truncation behavior (truncated: true), authentication error, and that results combine three categories. It also mentions the 'limit' parameter's effect (0 = unlimited).

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-loaded with purpose, and uses bullet points for parameters. Every sentence adds value 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 that an output schema exists and this is a list tool with few parameters, the description covers return fields (tarih, kategori, etc.), auth requirement, truncation, and parameter behavior comprehensively.

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

Parameters4/5

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

Despite 0% schema description coverage, the description explains both 'category' (if given, returns only that category) and 'limit' (default 50, 0 = unlimited, truncation flag) with sufficient detail beyond raw schema properties.

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 allergy records (E-Nabız alerji kayıtlarını listeler) and specifies it is read-only (salt-okunur). It also explains the three categories combined (ilac, tani, deri), distinguishing it from sibling tools that list 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?

The description provides guidance by noting authentication requirements (kimlikli oturum gerektirir) and behavior when category parameter is provided (yalnız o kategori döner). It does not explicitly exclude other tools, but the specialization to allergies is clear.

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