Skip to main content
Glama
zirve-finansman-mcp

zirve-finansman-mcp

by yibudak

demirbas_getir

Read-only

Retrieves an asset card by code with yearly valuation and depreciation lines, including beginning value, revaluation, period and accumulated depreciation, and net carrying value.

Instructions

Bir demirbaş kartını yıllık değerleme ve amortisman satırlarıyla getirir.

kod: demirbaş kodu (demirbas_ara sonucundaki Kod). yillar: her yıl için dönem başı değer, yeniden değerleme, dönem amortismanı (DonemAmortismani), birikmiş amortisman ve devreden net değer. Dikkat: yıllık satırları Zirve, Demirbaşlar > Raporlar ekranı çalıştırıldığında üretir; bazı yıllar eksik ya da güncel olmayabilir. Kesin tutar için muhasebe kaydına (muavin) bakı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": {
      "kod": "<kod>"
    },
    "name": "demirbas_getir"
  }
}

Input Schema

NameRequiredDescriptionDefault
kodYes
firmaNo

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?

Annotations already declare readOnlyHint=true, so the description does not need to re-establish safety. It adds genuinely non-obvious behavioral traits: the annual rows are only produced when the Zirve Demirbaşlar > Raporlar screen has been run, some years may be missing or stale, and authoritative figures live in the accounting entries. It does not discuss response envelope or pagination, but the reliability caveat is the higher-value disclosure here.

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?

The purpose is front-loaded in a single sentence, followed by per-field notes and then the caution. Wording is dense but earns its place; the only structural weakness is that the label-colon format used for 'kod' is reused for 'yillar', making an output description look like an input description.

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?

There is no output schema, and the description compensates by enumerating the per-year values returned (opening value, revaluation, period depreciation, accumulated depreciation, carried net value), which is exactly what an agent needs to interpret results. The remaining gap is the undocumented 'firma' parameter, which leaves scope ambiguity for multi-company scenarios.

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%, so the description must carry parameter meaning. It does well on 'kod' by tying it to the 'Kod' field of demirbas_ara output, but the second parameter 'firma' is never mentioned, and the 'yillar:' block reads like a parameter listing even though no such parameter exists in the schema, which could briefly mislead an agent about the accepted arguments.

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+resource: fetching a single fixed-asset card together with its annual revaluation and depreciation rows. It also implicitly separates itself from the sibling search tool by telling the agent that the required code comes from demirbas_ara results, so an agent can pick between search and fetch without opening either schema.

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 clear usage context by naming the prerequisite source of the 'kod' value (demirbas_ara output) and by routing the agent to the muavin sibling when exact accounting amounts are needed. It stops short of an explicit 'do not use this when…' exclusion, but the alternative-routing condition is stated in concrete terms.

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