Skip to main content
Glama

Calculate COD fee

calculate-cod-fee
Read-onlyIdempotent

Calculates the Sri Lanka Post cash on delivery (COD) fee for a parcel: the Logi Post courier fee for its weight, the money order commission on the amount collected, and the flat service fee. All amounts are in LKR.

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": {
      "weight_grams": "<weight_grams>",
      "amount_lkr": "<amount_lkr>"
    },
    "name": "calculate-cod-fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_lkrYesAmount the courier collects from the buyer, in LKR.
weight_gramsYesParcel weight in grams.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new context: the fee is composed of three named parts and denominated in LKR, which is important because there is no output schema to convey the result shape.

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?

A single sentence that front-loads the operation and resource, then enumerates the components with no filler. The currency note is short and load-bearing.

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?

For a two-parameter pure calculation with no output schema, the description gives enough: inputs' roles, fee components, and currency. It stops short of saying whether a total or an itemized breakdown is returned, which would fully close the gap left by the missing output schema.

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%, so both parameters are already documented as weight in grams and collected amount in LKR. The description reinforces the roles ('for its weight', 'on the amount collected') but adds no format, range, or rounding detail beyond the schema — baseline 3.

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?

States a specific verb and resource — calculates the Sri Lanka Post COD fee for a parcel — and itemizes the three components (courier fee by weight, money order commission, flat service fee), which clearly separates it from plain postage. It never names the sibling calculate-postage, so the differentiation is implicit rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is for quoting COD charges rather than ordinary postage, but the description never says when to call it versus calculate-postage, nor any prerequisite (e.g. that the amount must be the collectible sum).

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