Skip to main content
Glama

extract

by com.mart402
OverviewDiscussionsAdmin

Jp Mortgage

jp_mortgage
Idempotent

Mortgage schedules (level payment/principal), total interest, prepayment effect. $0.005/call. Deterministic, cites primary sources; errors and unverified rules are never billed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodNoOne of: level_payment, level_principal. Cost method: total_average or moving_averagelevel_payment
monthsYesLoan term in months
x_paymentNoOptional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged.
prepaymentNoOptional prepayment {at_month, amount_yen, mode: reduce_term|reduce_payment}
annual_rateYesAnnual interest rate as a decimal, e.g. 0.01
principal_yenYesLoan principal in yen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / method / default
      Added value: +"level_payment"
    • changedInput schema / properties / method / description
      Previous value: -"Cost method: total_average or moving_average"New value: +"One of: level_payment, level_principal. Cost method: total_average or moving_average"
    • addedInput schema / properties / method / enum
      Added value: +[
+  "level_payment",
+  "level_principal"
+]
    • changedInput schema / properties / months / description
      Previous value: -"See the product's input spec in /catalog"New value: +"Loan term in months"
    • changedInput schema / properties / prepayment / description
      Previous value: -"See the product's input spec in /catalog"New value: +"Optional prepayment {at_month, amount_yen, mode: reduce_term|reduce_payment}"
  2. Changed5 schema fields changed
    • addedInput schema / properties / annual_rate / description
      Added value: +"Annual interest rate as a decimal, e.g. 0.01"
    • addedInput schema / properties / method / description
      Added value: +"Cost method: total_average or moving_average"
    • addedInput schema / properties / months / description
      Added value: +"See the product's input spec in /catalog"
    • addedInput schema / properties / prepayment / description
      Added value: +"See the product's input spec in /catalog"
    • addedInput schema / properties / principal_yen / description
      Added value: +"Loan principal in yen"
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

The description adds valuable behavioral context beyond the minimal annotations (idempotentHint, readOnlyHint false). It discloses determinism, citation of primary sources, and a billing guarantee (errors/unverified rules never billed). This enriches the agent's understanding of reliability and cost behavior, though it does not mention any side effects or prerequisites beyond payment.

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?

The description is three sentences with zero filler: first sentence states the core function, second gives cost, third covers reliability. Key information is front-loaded, and every sentence earns its place. Exemplary conciseness.

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

Completeness3/5

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

No output schema exists, so the description should explain what is returned. It lists outputs (schedules, total interest, prepayment effect) but does not describe format, units, or edge cases. Given moderate complexity (6 params, nested object), it could benefit from more detail on output structure or assumptions, though it is adequate for a straightforward calculation tool.

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 covers all parameters with descriptions (100% coverage), so the baseline is 3. The description mentions level payment/principal and prepayment effect, which map to the method enum and prepayment object, but it does not add new meaning beyond the schema; it simply restates concepts already documented there.

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 clearly states the tool computes mortgage schedules with two methods (level payment/principal), total interest, and prepayment effect. It distinguishes from sibling tools like jp_tax and jp_bonus_net by narrowing to mortgage-specific calculations. The verb is implied but obvious from context.

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?

There is no explicit guidance on when to use this vs alternatives. The purpose implies it should be used for mortgage schedule calculations, but no alternative is named and no exclusions are provided. The mention of cost/determinism might help an agent decide based on those factors, but not directly about tool selection.

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

All extract toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources