Skip to main content
Glama
TurkActuary MCP

TurkActuary MCP

by afsharid

present_value

Read-onlyIdempotent

Calculates net present value from a series of cash flows using an explicit periodic discount rate, converting future amounts into today's value.

Instructions

Açık dönemlik oranla net bugünkü değer.

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": {
      "cashflows": "<cashflows>",
      "rate": "<rate>"
    },
    "name": "present_value"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 clear without the description. Beyond that, the description adds only the vague phrase "açık dönemlik oranla" — it does not clarify whether discounting is per-period, whether period 0 cashflows are undiscounted, how signs are handled, or what is returned.

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

Conciseness3/5

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

It is a single short sentence with no filler, and the key concept is front-loaded. The brevity, however, comes from omission rather than efficiency: the phrase "açık dönemlik" is ambiguous and the sentence earns its place only marginally.

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 calculation tool with two required parameters, no output schema, and an undocumented nested cashflow structure, the description should at least state the discounting convention and the expected result form. It does neither, leaving the agent to infer the financial semantics from a five-word sentence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: the rate field is documented, but the cashflows array itself, and its period and amount subfields, are undocumented (amount even repeats the rate wording about percentages). The description supplies no compensating information about expected cashflow shape, ordering, or the meaning of period 0.

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?

"Net bugünkü değer" identifies the computation (net present value) and "açık dönemlik oranla" hints at the discounting convention, so the domain is recognizable. However, there is no verb and no statement of what makes this different from sibling valuation tools such as annuity, life_annuity_pv or life_insurance_pv, so an agent cannot confidently route between them.

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?

The description gives no when-to-use guidance and no alternatives. With several present-value siblings in the catalog, the agent is left to guess whether arbitrary cashflow streams belong here rather than in annuity or life_annuity_pv.

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