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

E-Nabız MCP

by UmutKDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

enabiz_get_profile

Read-only

Retrieves profile summary including name, birth date, blood type, height, weight, and family doctor from E-Nabız health records. Requires authentication.

Instructions

E-Nabız profil özetini döndürür — salt-okunur.

Ad soyad, doğum tarihi, kan grubu, boy, kilo ve aile hekimi bilgisini döndürür. Gizlilik gereği TCKN, e-posta ve telefon dahil edilmez. Kimlikli oturum gerektirir; yoksa error: "auth_required".

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_get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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=true. The description adds that sensitive fields (TCKN, email, phone) are excluded and identifies an error case (auth_required). This provides useful behavioral context beyond the 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 three sentences, front-loaded with purpose, and uses bullet-like formatting to list returned/excluded fields. Every sentence provides value with no 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 the simplicity (no parameters, annotations present, output schema exists), the description completely covers return fields, exclusions, and authentication requirements. It is self-contained for an agent to use correctly.

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?

The input schema has zero parameters, so baseline is 4. The description adds no parameter info, but none is needed. The description is sufficient for a parameterless tool.

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 it returns the E-Nabız profile summary (verb+resource), lists included fields (name, blood type, etc.), and explicitly excludes sensitive data. This distinguishes it from sibling tools that focus on specific health records (e.g., diagnoses, prescriptions).

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 specifies that the tool requires an authenticated session and will error otherwise. It implies that it is for profile data only, but it does not explicitly say when not to use it or mention alternatives among the siblings.

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