Skip to main content
Glama
UseCOS MCP Server

UseCOS MCP Server

by rivlosys

compare_mortgage_renewals

Compare two or three Canadian mortgage renewal offers side by side to evaluate scheduled payments, term interest, principal paid, ending balance, switching costs, and total term cost.

Instructions

Deterministically compare 2 or 3 Canadian mortgage renewal offers by scheduled payment, term interest, principal paid, ending balance, switching costs, and total term cost.

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": {
      "position": "<position>",
      "offers": "<offers>"
    },
    "name": "compare_mortgage_renewals"
  }
}

Input Schema

NameRequiredDescriptionDefault
offersYes
positionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It adds useful context by stating the comparison is 'deterministic' and naming the output metrics, but it does not explain the return shape, whether an offer is ranked or recommended, or any calculation assumptions beyond the metric list.

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 definition is a single front-loaded sentence with no filler. It states the operation, constraint, domain, and comparison metrics efficiently.

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?

The tool has a complex nested input schema, no output schema, and no annotations, so the description needs to compensate with more parameter and behavioral context. It explains the high-level purpose but leaves the agent without guidance on populating the many offer and position fields or interpreting the comparison result.

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 the schema contains many nested offer fields with defaults and enums. The description only clarifies that 2 or 3 offers are compared and lists result dimensions; it does not explain required inputs such as position.renewalBalance, offers[].termYears, rateType, compounding, paymentFrequency, or cost fields.

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 uses a specific verb ('compare') and resource ('Canadian mortgage renewal offers'), sets scope at 2 or 3 offers, and lists the exact comparison dimensions. This makes clear that it is a comparison tool rather than a single-mortgage calculator like calculate_canadian_mortgage.

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?

The context implies use when comparing two or three Canadian mortgage renewal offers, and the 2-3 constraint is explicit. However, it does not state when to choose this over calculate_canadian_mortgage or any other alternative, nor does it provide exclusions.

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