Skip to main content
Glama
zirve-finansman-mcp

zirve-finansman-mcp

by yibudak

demirbas_ara

Read-only

Search fixed asset cards by name, code prefix, status, or purchase date range. Retrieve asset records and total purchase amounts for accounting lookup.

Instructions

Demirbaş (sabit kıymet) kartlarında arama yapar. Kartlar yıldan bağımsızdır, yil parametresi yoktur.

arama: demirbaş adında geçen metin. kod_on_eki: demirbaş kodu başlangıcı (çoğu kurulumda kod, demirbaşın muhasebe hesap koduyla aynıdır; ör. "253", "254.01"). durum: "hepsi", "aktif" (satılmamış) veya "satilan". alis_baslangic/alis_bitis: alış tarihi aralığı. toplam alanı sayfalamadan bağımsız adet ve alış tutarıdır. HesapKodu demirbaşın muhasebe hesabıdır; hareketleri için muavin(hesap_kodu=...) kullanın.

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

Input Schema

NameRequiredDescriptionDefault
aramaNo
durumNohepsi
firmaNo
limitNo
offsetNo
alis_bitisNo
kod_on_ekiNo
alis_baslangicNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint=true already declaring the safety profile, the description adds genuinely non-obvious behavior: cards are year-independent (no year filter exists at all), and the response's 'toplam' field is a count and purchase-total that is independent of pagination — important for anyone paginating. It does not discuss ordering of results or how firma scoping affects the search.

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 purpose and the year-independence constraint, then a compact parameter glossary. Almost every clause carries information; the only mild waste is that limit/offset are omitted while lower-value details are included.

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, zero-schema-coverage, no-output-schema tool, the description covers five parameters plus one return-field caveat, which is substantial. The gap is 'firma' — a filter whose meaning (which company's asset register) is never explained anywhere, despite being arguably decisive for correct invocation.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry the semantics and it largely does: arama, kod_on_eki (including the concrete hint that codes usually equal the accounting account code, e.g. "253", "254.01"), durum with its three accepted values (the schema has no enum), and the alis_baslangic/alis_bitis date range. Three parameters — firma, limit, offset — are left entirely undocumented in both description and schema.

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?

The description opens with a specific verb and resource (searching fixed-asset/"demirbaş" cards) and immediately scopes it with "Kartlar yıldan bağımsızdır, yil parametresi yoktur", which prevents a common wrong assumption. It also distinguishes the resource from its ledger counterpart by naming muavin for movement/transaction data.

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?

It gives an explicit alternative with a selecting condition: for the asset's accounting movements, use muavin(hesap_kodu=...). Usage for the durum values is also spelled out (hepsi/aktif=satılmamış/satilan). It does not say when to prefer demirbas_getir over this search, so routing to one sibling remains implicit.

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