Skip to main content
Glama

Annual Coupon Bond Price

bpj_annual_coupon_bond_price
Read-onlyIdempotent

Discount annual coupon payments and redemption at par, valued on a coupon date with complete years remaining.

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": {
      "face": "<face>",
      "coupon": "<coupon>",
      "yieldRate": "<yieldRate>",
      "years": "<years>"
    },
    "name": "bpj_annual_coupon_bond_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
faceYes
yearsYes
couponYes
yieldRateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, closed-world calculation. The description adds the valuation convention, but it does not state the return format, rounding behavior, or what happens outside the stated coupon-date and whole-year assumptions.

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 dense sentence with no wasted words and the core calculation is front-loaded. The valuation assumptions are packed efficiently into the sentence.

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 four-parameter bond-pricing calculator with no output schema, the description gives the main valuation assumptions but leaves important invocation context unstated. It does not explain the expected return value or fully document parameter meanings, so an agent must rely on the schema titles and domain knowledge.

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%, so the description must compensate for all four parameters. It indirectly implies the coupon, redemption at par, and whole-year horizon, but it never mentions the yield rate or clearly maps face value, coupon rate, yield, and years to their roles in the calculation.

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?

The description states a specific calculation: discounting annual coupon payments and redemption at par for a bond valued on a coupon date with complete years remaining. The resource and method are clear, but it does not explicitly differentiate this tool from nearby bond-related siblings such as cashflow duration or effective annual yield.

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 phrase 'valued on a coupon date with complete years remaining' provides an important applicability constraint, implying the tool should be used only under those conditions. However, there is no explicit when-to-use guidance, no exclusions, and no named alternatives for related bond calculations.

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.