Skip to main content
Glama

calculate_finance

Read-onlyIdempotent

Vooraf te financieren bedrag en vaste maandtermijn. Trek premie alleen af als al ontvangen. Nominale jaarrente, geen JKP, dossierkosten of latere aflossing.

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": {
      "budget": "<budget>",
      "savings": "<savings>",
      "premieAmount": "<premieAmount>",
      "premieReceived": "<premieReceived>",
      "annualRate": "<annualRate>",
      "months": "<months>"
    },
    "name": "calculate_finance"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetYes
monthsYes
savingsYes
annualRateYes
premieAmountYes
premieReceivedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior4/5

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

The annotations already declare this as a read-only, idempotent, non-destructive calculation, so the description's main job is to add domain behavior. It does add valuable calculation rules: deduct the premium only if already received, use nominal annual interest, and exclude JKP, dossierkosten, and later repayment. It does not explain return format, but with annotations covering safety this is a solid behavioral disclosure.

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?

The description is very short, front-loads the output targets, and adds calculation assumptions without filler. Its telegraphic phrasing is somewhat cryptic, but it does not waste space.

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 six-parameter financial calculator with no output schema and 0% schema description coverage, the definition should make the input meanings and calculation scope explicit. It provides useful assumptions but omits parameter-level semantics, so an agent cannot confidently map each required input.

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 0% and all six parameters are required, so the description needs to compensate heavily. It only indirectly clarifies premieReceived ('alleen af als al ontvangen') and annualRate ('nominale jaarrente'); budget, savings, premieAmount, and months remain undefined, leaving most parameter meaning to inference.

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 names the outputs ('Vooraf te financieren bedrag en vaste maandtermijn') and some calculation caveats, but it never states a clear verb like 'calculate' or identifies the resource being computed. With several sibling calculate_* tools, an agent gets only a vague sense of what this tool computes versus the alternatives.

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 explicit guidance on when to use this tool instead of calculate_budget, calculate_premie, or other siblings, and no stated prerequisites. The calculation assumptions are useful but do not tell the agent when this tool is the right choice.

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