Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

房贷月供计算(等额本息)

mortgage-monthly

房贷月供计算(等额本息):按贷款本金、年限、年利率算等额本息月供、总还款、总利息。公式固定,不碰 LPR 实时数据与各地政策。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "principal": "<principal>",
      "years": "<years>",
      "annualRate": "<annualRate>"
    },
    "name": "mortgage-monthly"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsYes贷款年限
principalYes贷款本金(元)
annualRateYes年利率(%,如 3.5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose that the formula is fixed, the output is deterministic, a rationale is returned with the numbers, and no live rate or policy data is consulted. It does not state side-effect freedom explicitly or mention rounding/precision conventions, which leaves a small gap for a pure calculator.

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 purpose and scope are front-loaded and the whole entry is compact. The sentence about passing a parameter object and getting a deterministic result with rationale is slightly redundant with the preceding scope statement, but it is not enough to hurt readability.

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?

There is no output schema, but the description enumerates the return values (monthly payment, total repayment, total interest) and marks the tool as deterministic, which is what an agent needs. Missing niceties are rounding precision and treatment of a zero-rate or fractional-year input, which are minor for a three-parameter calculator.

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 100%, so principal, years, and annualRate are already documented in the schema, including that the rate is a percentage like 3.5. The description restates the same three inputs without adding syntax, unit, or range guidance beyond that, so baseline 3 applies.

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 a specific verb and resource: compute the equal-installment (等额本息) monthly payment, total repayment, and total interest from principal, term, and annual rate. It also draws an explicit boundary against LPR data and regional policies, so an agent can tell it apart from contract/deposit siblings on the list.

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?

It states a clear trigger: use this when model arithmetic is unreliable or when regulatory interpretation is error-prone, and take the answer from here. It also implicitly scopes out real-time LPR and local policy questions. It does not, however, name a concrete alternative tool for those out-of-scope cases, so routing is only partly resolved.

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