Skip to main content
Glama

Yüzde

yuzde_hesapla
Read-onlyIdempotent

Yüzde hesabı. yuzdesi: A'nın %B'si; yuzde-kaci: A, B'nin yüzde kaçı; degisim: A'dan B'ye yüzde değişim.

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": {
      "islem": "<islem>",
      "a": "<a>",
      "b": "<b>"
    },
    "name": "yuzde_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesyuzdesi: sayı; yuzde-kaci: parça; degisim: eski değer.
bYesyuzdesi: oran; yuzde-kaci: bütün; degisim: yeni değer.
islemYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / a / description
      Previous value: -"Birinci sayı (yuzdesi: sayı; yuzde-kaci: parça; degisim: başlangıç değeri)."New value: +"yuzdesi: sayı; yuzde-kaci: parça; degisim: eski değer."
    • changedInput schema / properties / b / description
      Previous value: -"İkinci sayı (yuzdesi: yüzde oranı; yuzde-kaci: bütün; degisim: yeni değer)."New value: +"yuzdesi: oran; yuzde-kaci: bütün; degisim: yeni değer."
    • removedInput schema / properties / islem / description
      Removed value: -"yuzdesi, yuzde-kaci ya da degisim."
  2. First observed

TDQS

A3.6/5.0
Behavior2/5

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

The annotations already state that the tool is read-only, idempotent, non-destructive, and closed-world. The description adds no behavioral context beyond the mathematical formulas, such as rounding behavior, precision, output format, or zero/negative input handling.

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?

The description is two compact sentences with front-loaded purpose and semicolon-separated mode definitions. Every phrase contributes directly to explaining the tool's operations.

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 a simple three-parameter calculator, the operational formulas are well covered. However, there is no output schema and the description does not explain the return value format, rounding, or edge-case behavior, leaving some ambiguity for an invoking agent.

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 67%, and the enum parameter lacks a schema-level description. The description compensates by defining the exact relationship between a and b for each of the three operation modes, adding substantial meaning beyond the parameter names.

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?

The description clearly states that this is a percentage calculation tool and names three distinct calculation modes with concise formulas. It does not explicitly differentiate itself from the many domain-specific calculator siblings, so it falls short of a 5.

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?

The description effectively explains when each islem mode should be used by defining what each mode computes. It does not mention when not to use this generic tool versus more specific calculators such as kdv_hesapla or kira_artis_hesapla, but no false guidance is given.

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