Skip to main content
Glama
TurkActuary MCP

TurkActuary MCP

by afsharid

annuity

Read-onlyIdempotent

Calculates the value of equal payments made at the start or end of each period from payment amount, interest rate, and period count.

Instructions

Dönem sonu veya başı sabit ödeme annüitesi.

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": {
      "payment": "<payment>",
      "rate": "<rate>",
      "periods": "<periods>"
    },
    "name": "annuity"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYesSonlu ondalık; oranlar yüzde değil (0.10 = %10).
timingNo
paymentYesSonlu ondalık; oranlar yüzde değil (0.10 = %10).
periodsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered and the description need not repeat it. What the description fails to add is the thing annotations cannot convey: since there is no output schema, it should say what value is computed and returned. The only behavioral content it adds is that payments are level and timing can be period-end or period-beginning.

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?

A single compact sentence with no filler, and the discriminating detail (period-end vs. period-beginning) is placed up front. It is efficient rather than padded, though its brevity edges into under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter financial calculator with no output schema, the description leaves the most important question unanswered: what the returned figure is and in what units. It also omits any note on the periods bound or how the three required inputs combine, so an agent must guess at the tool's output semantics.

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 50%: rate and payment carry schema descriptions, while timing and periods do not. The description partially compensates by glossing timing as 'dönem sonu veya başı', which clarifies the immediate/due enum, but it says nothing about periods or its 1–10000 bound, nor about the relationship between payment and rate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the object ('sabit ödeme annüitesi' – fixed-payment annuity) and the timing dimension (end vs. beginning of period), but never states the operation: it does not say whether it returns a present value, future value, or payment amount. With siblings such as present_value and life_annuity_pv in the catalog, an agent cannot tell from the text which result this tool produces.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusion of alternatives, and no mention of when an agent should pick this over present_value or life_annuity_pv. The only implied usage is the ordinary-vs-due distinction, which is left for the agent to infer.

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