Skip to main content
Glama

Cash For My Note Calculators

Effective annual rate calculator

effective_annual_rate
Read-onlyIdempotent

The effective annual rate is what a nominal annual rate compounded monthly actually earns over a year, and this tool converts one into the other. Estimates, not offers or appraisals. CashForMyNote.com does not buy notes or make offers.

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": {
      "nominal_rate": "<nominal_rate>"
    },
    "name": "effective_annual_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
nominal_rateYesNominal annual %, monthly compounding.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only a legal disclaimer (estimates, not offers, CashForMyNote.com does not buy notes) and no substantive behavior such as output format, rounding, or formula assumptions beyond 'compounded monthly'.

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?

Two compact sentences with no filler, and the definition is front-loaded. The disclaimer occupies half the text, which is defensible for a consumer-finance site but dilutes the functional content.

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?

For a single-parameter, no-output-schema tool, the description should at least say what the returned number represents (percentage vs. decimal) and whether it is rounded. It omits that and spends its remaining space on a disclaimer, so the agent must guess the return convention.

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 coverage is 100% with a single documented parameter, so the baseline of 3 applies. The description's phrase 'nominal annual rate compounded monthly' restates rather than extends the schema's own 'Nominal annual %, monthly compounding.'

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 resource (effective annual rate) and states a conversion intent, but 'converts one into the other' implies bidirectionality while the schema accepts only nominal_rate, leaving the actual operation slightly ambiguous. It never states plainly 'given a nominal rate, return the effective rate,' and it does not distinguish itself from siblings like rate_vs_market or market_rates.

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?

No when-to-use guidance is given beyond the implicit definition; nothing says when an agent should pick this over rate_vs_market, market_rates, or note_yield. There are no preconditions or exclusions stated.

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