Skip to main content
Glama

Kargo desi

kargo_desi_hesapla
Read-onlyIdempotent

Kolilerin desisini (en × boy × yükseklik ÷ 3000) ve ücrete esas ağırlığı (desi ile kilodan büyüğü) hesaplar. TL ücret vermez.

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": {
      "koliler": "<koliler>"
    },
    "name": "kargo_desi_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
kolilerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / koliler / description
      Removed value: -"Koliler. Her koli: en, boy, yukseklik (cm), agirlik (kg) ve isteğe bağlı adet (varsayılan 1)."
    • changedInput schema / properties / koliler / items / properties / adet / description
      Previous value: -"Bu koliden kaç tane. Varsayılan 1."New value: +"Varsayılan 1."
    • changedInput schema / properties / koliler / items / properties / agirlik / description
      Previous value: -"Gerçek ağırlık (kg)."New value: +"kg"
    • changedInput schema / properties / koliler / items / properties / boy / description
      Previous value: -"Boy (cm)."New value: +"cm"
    • changedInput schema / properties / koliler / items / properties / en / description
      Previous value: -"En (cm)."New value: +"cm"
    • changedInput schema / properties / koliler / items / properties / yukseklik / description
      Previous value: -"Yükseklik (cm)."New value: +"cm"
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world calculation, so safety is covered. The description adds real behavioral value beyond them by disclosing the divisor (3000) and that the chargeable weight is the greater of desi and actual kg. It does not state rounding/precision rules, which is the main remaining behavioral gap.

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 short sentences, front-loaded with the core computation, followed by the scope exclusion. No filler and nothing repeated from the schema.

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?

With no output schema, the description does state what is produced (desi and chargeable weight), which is enough to understand the return. It falls short on aggregation across multiple packages, per-box quantity handling, and rounding, all of which an agent would need in order to interpret results confidently.

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 reported as 0%, so the description must carry the semantics, and it does map its formula terms onto en, boy, yukseklik and kilo. However it never explains the 'adet' (quantity) field — whether desi is multiplied per box or whether results are summed across the 'koliler' array — which is the most consequential interpretation question for a multi-package tool.

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 names two precise outputs (desi and 'ücrete esas ağırlık') and even gives the formula (en × boy × yükseklik ÷ 3000), which leaves no doubt about the resource being computed. It also draws a boundary against the other calculators in the catalog by stating it returns no TL price.

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?

There is a clear usage context (volumetric/chargeable weight for parcels) plus an explicit exclusion ('TL ücret vermez'), which steers an agent away from expecting pricing. What is missing is a named alternative for the pricing step, so the routing hint is only partial.

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