Skip to main content
Glama

Kâr marjı

kar_marji_hesapla
Read-onlyIdempotent

Birim maliyet ve satış fiyatından toplam kâr/zararı, kâr marjını (kâr ÷ ciro) ve markup'ı (kâr ÷ maliyet) hesaplar. KDV, komisyon ya da kargo eklemez.

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": {
      "maliyet": "<maliyet>",
      "satisFiyati": "<satisFiyati>"
    },
    "name": "kar_marji_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
adetNoAdet. Varsayılan 1.
maliyetYesBirim (TL).
satisFiyatiYesBirim (TL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / maliyet / description
      Previous value: -"Birim maliyet (TL)."New value: +"Birim (TL)."
    • changedInput schema / properties / satisFiyati / description
      Previous value: -"Birim satış fiyatı (TL)."New value: +"Birim (TL)."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description's main job is scope disclosure. It does that well by pinning the formulas and excluding extra cost components, which prevents the agent from expecting VAT-inclusive results. It does not address edge cases such as zero sale price, where the margin division would fail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler: the first front-loads the outputs and their formulas, the second front-loads the scope boundary. Nothing is repeated from the schema or annotations.

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?

With no output schema, the description correctly enumerates the three returned values, which is the essential information. The gaps are the unmentioned quantity parameter and no note on division-by-zero when satisFiyati is 0, which the schema explicitly permits.

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 100% and every parameter carries a description, so the baseline of 3 applies. The description adds the semantic distinction between margin and markup, but it never mentions the optional 'adet' (quantity) parameter, leaving ambiguous whether the stated 'total profit/loss' is per unit or multiplied by quantity.

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 specific computation (total profit/loss, profit margin = profit ÷ revenue, markup = profit ÷ cost) from unit cost and sale price, so the verb and outputs are unambiguous. The closing exclusion (no VAT, commission, or shipping) separates it from siblings such as kdv_hesapla or kargo-related tools.

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?

Tells the agent when this tool is the wrong fit by declaring what it does NOT include, so tax or logistics costs must be computed elsewhere. It never names a concrete alternative sibling or states prerequisites, so routing is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources