Skip to main content
Glama
zirve-finansman-mcp

zirve-finansman-mcp

by yibudak

hesap_ara

Read-only

Searches the chart of accounts, including current accounts, by account name, code prefix, tax ID, or detail-only filters to locate the right account code.

Instructions

Hesap planında arama yapar (cari hesaplar dahil; ör. 120=alıcılar, 320=satıcılar).

arama: hesap adında geçen metin (büyük-küçük harf ve Türkçe karakter ayrımı gözetmez). kod_on_eki: hesap kodu başlangıcı (ör. "120" veya "320.01"). vergi_no: hesaba tanımlı VKN/TCKN. sadece_detay: yalnızca kayıt girilebilen alt hesaplar. Hesap kartlarının çoğunda VKN boştur; vergi_no ile sonuç çıkmazsa yevmiye_ara(vergi_no=..., hesap_on_eki="120" veya "320") ile carinin hesap kodunu yevmiye satırlarından bulun.

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": "hesap_ara"
  }
}

Input Schema

NameRequiredDescriptionDefault
yilNo
aramaNo
firmaNo
limitNo
offsetNo
vergi_noNo
kod_on_ekiNo
sadece_detayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

readOnlyHint:true is consistent, and the description adds behavior beyond annotations: the default sadece_detay=true restricts results to postable sub-accounts, and the note that VKN is usually blank warns the agent that a tax-number search often returns nothing. It stops short of describing result format or pagination behavior, which is acceptable since annotations cover the safety profile.

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?

Opens with a one-line purpose and then a compact parameter glossary, each line earning its place. The fallback advice is appended without padding, though the mixed narrative/list layout is slightly harder to scan than a clean split.

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?

For an eight-parameter, no-output-schema lookup tool this covers the semantics that matter most, including the trap around empty VKN fields and the meaning of the detail-only default. The main remaining gap is that the company/year scoping parameters are never explained, which matters for a multi-company accounting system.

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%, so the description carries the burden; it documents four of eight parameters (arama, kod_on_eki, vergi_no, sadece_detay) with useful semantics such as case- and Turkish-character-insensitive matching and prefix format examples. However, yil, firma, limit and offset are undocumented in both places, leaving half the surface unexplained.

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?

States a specific verb and resource ('Hesap planında arama yapar') plus scope ('cari hesaplar dahil') and concrete examples (120=alıcılar, 320=satıcılar), so the agent knows exactly which domain object is searched. It is clearly distinguishable from siblings like yevmiye_ara or demirbas_ara from the text alone.

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?

Gives an explicit fallback path: if vergi_no returns nothing (common because most account cards have an empty VKN), use yevmiye_ara with vergi_no and hesap_on_eki 120/320 to resolve the cari's code from journal lines. That is real routing guidance, though it does not cover when to prefer this over other search-style siblings in general.

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