Skip to main content
Glama
zirve-finansman-mcp

zirve-finansman-mcp

by yibudak

muavin

Read-only

Retrieve a single general-ledger account's movements and running balance, summarize prior activity as an opening balance from a start date, and choose whether to include closing entries.

Instructions

Muavin (hesap ekstresi): tek bir hesabın hareketleri ve yürüyen bakiyesi.

hesap_kodu: tam hesap kodu (ör. "120.00010"; hesap_ara ile bulunur). baslangic verilirse o tarihten önceki hareketler "devreden" olarak özetlenir. Bakiye pozitifse borç, negatifse alacak bakiyesidir. kapanis_dahil: mizan ile tutarlı olsun diye kapanış fişi (Fistur 9) varsayılan olarak sayılmaz; True verilirse kapanmış yılda kapanış bakiyesi sıfır çıkar. Ana hesap ya da olmayan kod verilirse hata döner.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hesap_kodu": "<hesap_kodu>"
    },
    "name": "muavin"
  }
}

Input Schema

NameRequiredDescriptionDefault
yilNo
bitisNo
firmaNo
limitNo
offsetNo
baslangicNo
hesap_koduYes
kapanis_dahilNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real behavior beyond that: pre-baslangic movements collapse into a single "devreden" row, the closing voucher (Fistur 9) is excluded by default so the closing balance reads zero in a closed year, and sign convention maps to borç/alacak. It stays silent on pagination behavior despite limit/offset defaults, which is the main remaining gap.

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 a one-line definition, then parameter notes in the order an agent needs them. Dense but every sentence carries content; the only softness is that the hesap_kodu and error sentences could be tightened into one.

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 an 8-parameter accounting tool with no output schema, the description covers the domain-critical semantics (account code resolution, opening-entry folding, closing-entry exclusion) but omits date-range parameter interplay (yil vs baslangic/bitis) and the response shape beyond "running balance". Adequate to call correctly with defaults, incomplete for filtered queries.

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 coverage is 0% across 8 parameters, so the description must compensate. It explains the three least obvious ones (hesap_kodu format with a concrete example, baslangic aggregation semantics, kapanis_dahil default behavior), but yil, bitis, firma, limit and offset are never mentioned, leaving over half the surface undocumented.

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?

Names the resource and the exact output concept ("tek bir hesabın hareketleri ve yürüyen bakiyesi"), which separates it immediately from mizan (trial balance) and hesap_ara (code lookup). An agent knows this returns per-account movements with a running balance, not an aggregate.

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?

Routes the agent to hesap_ara for obtaining hesap_kodu and explains the mizan-consistency reason for the kapanis_dahil default, which is genuine when/when-not guidance. It also names failure conditions (ana hesap or nonexistent code returns an error). No explicit statement of when to prefer mizan or fisleri_listele instead, so not a full 5.

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