Skip to main content
Glama
zirve-finansman-mcp

zirve-finansman-mcp

by yibudak

mizan

Read-only

Calculates account-level debit, credit, and balance totals from journal lines, with filters for date range, account prefix, detail level, and optional closing entries.

Instructions

Mizan: hesap bazında borç/alacak toplamları ve bakiye (yevmiye satırlarından hesaplanır).

kod_on_eki: yalnızca bu kodla başlayan hesaplar (ör. "120"). baslangic/bitis: fiş tarihi aralığı (boşsa tüm yıl; açılış fişi 1 Ocak tarihlidir). seviye: "detay" (alt hesap) veya "ana" (ilk 3 hane). Bakiye = Borc - Alacak (pozitif borç bakiyesi). toplam alanı sayfalamadan bağımsız genel toplamdır. kapanis_dahil: Zirve'nin "kapanış fişi hariç" mizanı gibi, varsayılan olarak kapanış fişi (Fistur 9) sayılmaz; True verilirse kapanmış yıllarda tüm bakiyeler sıfırlanı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": "mizan"
  }
}

Input Schema

NameRequiredDescriptionDefault
yilNo
bitisNo
firmaNo
limitNo
offsetNo
seviyeNodetay
baslangicNo
kod_on_ekiNo
kapanis_dahilNo
sifir_bakiyelerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the burden and does well: it defines the balance formula (Borc - Alacak, positive = debit), states that toplam is a grand total independent of pagination, and discloses that closing entries (Fistur 9) are excluded by default unless kapanis_dahil is true, which zeroes balances in closed years. That is exactly the kind of default behavior an agent cannot see in structured fields. It stops short of describing output shape or the effect of firma/yil, preventing a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the one-line purpose, then parameter notes in a compact telegraphic style with no filler. Every clause carries information. It reads as a dense spec rather than prose, which slightly hurts scanability but not efficiency.

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

Completeness3/5

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

For a 10-parameter aggregation tool with no output schema and only a readOnly hint, the description is only partly sufficient. It covers the non-obvious filters and one return field (toplam), but leaves yil vs. baslangic/bitis overlap, firma scoping, and sifir_bakiyeler behavior undefined, forcing guesswork on a third of the inputs.

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 0% across 10 parameters, so the description must supply all meaning. It explains kod_on_eki, baslangic/bitis, seviye (including the enum-like values "detay"/"ana" and the first-3-digits rule), and kapanis_dahil in real detail, but leaves yil, firma, sifir_bakiyeler, limit and offset unaddressed. Roughly half the surface is compensated, which is adequate but incomplete.

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 names a concrete resource and operation: account-level debit/credit totals and balance, explicitly computed from journal lines ("yevmiye satırlarından hesaplanır"). That is far more specific than the bare name "mizan". It does not, however, contrast itself with siblings such as muavin or yevmiye_ara, so an agent must infer the split.

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 usage context is only implied: this is the reporting tool that aggregates a trial balance, while yevmiye_ara and muavin presumably list raw lines or subsidiary detail. No sentence says when to prefer this over those alternatives, and there is no when-not guidance. The parameter-level notes are helpful but are not usage routing.

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