Skip to main content
Glama

Effective Annual Yield

bpj_effective_annual_yield
Read-onlyIdempotent

Convert a nominal annual rate and compounding frequency into the periodic rate and effective annual yield.

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": "<nominal>",
      "periods": "<periods>"
    },
    "name": "bpj_effective_annual_yield"
  }
}

Input Schema

NameRequiredDescriptionDefault
nominalYes
periodsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered by structured data. Beyond that the description only discloses that two derived quantities are returned; it says nothing about output format, precision, or how rounding is handled.

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?

One sentence, zero filler, with the transformation front-loaded before any detail. Nothing is repeated from the schema beyond the parameter names needed to state the operation.

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?

For a simple two-parameter deterministic calculation with annotations and a bounded schema, the definition is nearly sufficient — the operation and both outputs are named. The remaining gap is that the returned values' units (percent vs. decimal fraction) are never stated, which matters for a yield number.

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 0%, but the schema titles ('Nominal annual rate (%)', 'Compounding periods per year') plus min/max bounds carry most of the semantic load. The description restates both parameters in natural language without adding anything new — such as confirming the percent scale or the per-year convention for periods.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ('Convert') plus clearly named inputs and outputs: nominal annual rate + compounding frequency in, periodic rate and effective annual yield out. Distinguishable from any sibling by resource domain (rate conversion), though it does not name or differentiate against any related tool.

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?

Arises implicitly from the stated inputs and outputs — an agent can infer it should use this when converting a nominal rate with a known compounding frequency. There is no explicit when-to-use, no prerequisites (e.g. rate expressed in percent), and no named alternative.

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.