Skip to main content
Glama
zirve-finansman-mcp

zirve-finansman-mcp

by yibudak

fis_getir

Read-only

Retrieves a single accounting voucher by Refno, returning its header and paginated journal lines for ledger review and reconciliation.

Instructions

Tek bir muhasebe fişini başlığı ve yevmiye satırlarıyla getirir (satırlar sayfalıdır).

refno: fişin Refno değeri (yevmiye_ara, muavin ve fisleri_listele sonuçlarında bulunur). satir_sayisi fişteki toplam satırdır; devami_var ise sonraki_offset ile devam edin. Not: Zirve'de bir fiş düzeltildiğinde Refno değişir; kalıcı referans olarak Fisno kullanın.

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": {
      "refno": "<refno>"
    },
    "name": "fis_getir"
  }
}

Input Schema

NameRequiredDescriptionDefault
yilNo
firmaNo
limitNo
refnoYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, so the description carries most of the burden and does add real value: it discloses that lines are paginated and that Refno mutates when a voucher is edited, recommending Fisno as the stable reference. It reveals two response fields (satir_sayisi, devami_var) without a full return shape, which is acceptable given there is no output schema.

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-loads the core action, then a compact parameter note and a caveat note. Every sentence carries information, though the offset naming mismatch adds a small ambiguity for callers.

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?

No output schema exists, so the description should describe returns more fully; it names only two fields. With 5 parameters and no schema descriptions, yil, firma and limit remain unexplained, leaving a caller unsure about year/company scoping.

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 5 parameters, so the description must compensate. It explains refno well and covers offset implicitly through the pagination note, but limit, yil and firma are never mentioned, and 'sonraki_offset' does not match the schema's 'offset' name exactly.

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?

States a specific verb and resource: fetch a single accounting voucher with its header and journal (yevmiye) lines. The singular 'tek bir ... fişi' implicitly contrasts with the listing siblings, but no sibling is named, so differentiation is inferred rather than stated.

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 concrete sourcing guidance: the refno can be found in the results of yevmiye_ara, muavin and fisleri_listele. It also explains the pagination loop (total lines in satir_sayisi, continue with sonraki_offset when devami_var). No explicit when-not-to-use case is given.

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