Skip to main content
Glama
ubaranzorlu
by ubaranzorlu

fonzip_ecards

Destructive

Manage donation e-cards and their transactions: create, update, and delete card categories; list, retrieve, and delete e-card sales with filters for date, payment, status, and delivery.

Instructions

E-kartlar: kart ve kart kategorisi yonetimi, e-kart satis islemlerini listeleme, detay ve silme.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listNo[list_transactions] *(paid only)* Selects the optional fields returned for each transaction. Repeat the parameter to request several fields, e.g. `?list=ecard&list=amount&list=category`. Every response always contains this base set, whatever `list` holds: `id`, `user_id`, `first_name`, `last_name`, `email`, `phone`, `certificate_id`, `ce…
nameNo[create_category, update_category] Donation/E-Card Category name
queryNo[list, list_categories, list_transactions] search parameter. start with - (minus) char to exclude searched text
actionYesYapilacak islem. Her action'in kendi zorunlu alanlari vardir; asagidaki aciklamalarda hangi alanin hangi action'a ait oldugu koseli parantez icinde belirtilir.
amountNo[list_transactions] payment/debt amount
statusNo[list_transactions] E-Card Transaction status. Defaults to `paid` when omitted. Any other value is rejected with HTTP 400. - paid: successful E-Card transactions - refund: refunded E-Card transactions - failed: failed E-Card transactionspaid
amt_cndNo[list_transactions] amount condition if amount filter is present - null: equals to amount - !=: not equals to amount - <: smaller than amount - <=: smaller and equal to amount - \>: bigger than amount - \>=: bigger and equal to amount
listingNo[list] E-Card available for sale in E-Card page - 0: private - 1: available - 2: available only via url
sale_idNo[delete_transaction, get_transaction] Zorunlu: delete_transaction, get_transaction.
ecard_idNo[get, list_transactions] Zorunlu: get.
end_dateNo[list_transactions] Zorunlu: list_transactions. End date filtering for transaction__complete_date or complete_date fields. Must be after start_date.
how_manyNo[list, list_categories, list_transactions] How many records should be listed
order_byNo[list_transactions] Ordering. Any field of the `CertificateSale` model (or a `transaction__` / `certificate__` related field) is accepted; an unknown field is rejected with HTTP 400. Rows are always tie-broken by `id`. The default depends on `status`: `-transaction__refund_date` for `refund`, `-transaction__complete_date` for `paid` and…-transaction__complete_date
bill_typeNo[list_transactions] *(paid only)* filter on the requested billing information type - 0: no bill - 1: personal - 2: corporate
card_typeNo[list_transactions] *(paid only)* filter card payments on card type. Any other value is rejected with HTTP 400. - 1: credit - 2: debit - 3: prepaid - 4: unknown (BIN not recognised)
last_fourNo[list_transactions] card last four digits
bin_numberNo[list_transactions] card BIN number
start_dateNo[list_transactions] Zorunlu: list_transactions. Start date filtering for transaction__complete_date or complete_date fields. Must be before end_date.
start_pageNo[list, list_categories, list_transactions] start page of records
utm_mediumNo[list_transactions] *(paid only)* Filter e-card transactions by one or more `utm_medium` values (IN-list).
utm_sourceNo[list_transactions] *(paid only)* Filter e-card transactions whose marketing channel `utm_source` matches one of the supplied values (IN-list). Repeat the parameter to supply multiple values, e.g. `?utm_source=google&utm_source=bing`.
category_idNo[delete_category, list, update_category] Zorunlu: delete_category, update_category.
currency_idNo[list_transactions] *(paid only)* filter transactions on currency id
utm_contentNo[list_transactions] *(paid only)* Filter e-card transactions by one or more `utm_content` values (IN-list).
card_countryNo[list_transactions] *(paid only)* filter card payments on the issuing bank's country, relative to the association's own country. Any other value is rejected with HTTP 400. - 1: local (issued in the association's country) - 2: abroad - 3: unknown (BIN not recognised)
cargo_statusNo[list_transactions] *(paid only)* filter based on cargo status - null: all - 0: will not be sent - 1: waiting to be prepared - 2: waiting for cargo info - 3: posted - 4: waiting to be prepared **or** waiting for cargo info (1 and 2 combined)
utm_campaignNo[list_transactions] *(paid only)* Filter e-card transactions by one or more `utm_campaign` values (IN-list).
delivery_dateNo[list_transactions] *(paid only)* Return only transactions scheduled for future delivery (`delivery_time_mode` 1 or 2) whose delivery date - either on the transaction itself or on one of its recipients - equals this date. Sent as a date-time; it is converted to the association timezone and compared as a date.
payment_methodNo[list_transactions] payment type code - null: All - 0: Card - 1: Cash - 2: Wire Transfer - 3: POS - 4: SMS - 6: Postal Check - 7: Paypal - 8: BKM Express - 9: iDEAL - 10: Pay With Iyzico
bank_account_idNo[list_transactions] *(paid only)* bank account id
payment_settings_idNo[list_transactions] *(paid only)* payment settings id
marketing_channel_nullNo[list_transactions] *(paid only)* When true, return only e-card transactions with no marketing channel attached (organic / direct traffic). Mutually exclusive with the four UTM filters above — when set, those are ignored.
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the bar is lower. The description adds some context by stating that sales transactions can be deleted ('silme'), which tells the agent what kind of destructive action exists. However, it does not disclose anything beyond that—no permissions, reversibility, or side effects—so it only partially fulfills this dimension.

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 a single compact sentence that front-loads the resource and the three main operation types. Every word earns its place, with no repetition of schema details or annotations. This is appropriately concise for a tool with such a rich input schema.

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?

The input schema is exceptionally detailed—every parameter is documented with action tags, enums, defaults, and constraints—so the short description does not need to compensate for missing parameter context. The combination of description and schema gives an agent enough orientation to select the correct action and required fields. It is not a 5 because the description alone does not summarize all nine actions or warn about the destructive operations beyond a passing 'silme' mention.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents every parameter's meaning and usage per action. The description itself adds no parameter-level information, which is acceptable but not value-adding. Baseline 3 applies here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a clear resource domain ('E-kartlar') and enumerates the operation groups: card/category management and listing, detail, and deletion of e-card sales transactions. This maps well onto the action enum (create_category, update_category, delete_category, list, get, list_transactions, get_transaction, delete_transaction) and distinguishes the tool from fonzip_* siblings by its e-card focus. It loses one point because 'yonetimi' (management) is a broad verb and does not explicitly name create/update actions.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as fonzip_donations or fonzip_events, and no exclusions or preferred scenarios. The only implied distinction is the e-card resource in the name, which is not enough for an agent to know when to choose this over sibling tools.

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/ubaranzorlu/fonzip-mcp'

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