Skip to main content
Glama

Foreign Payable Hedge Blend

bpj_foreign_payable_hedge_blend
Read-onlyIdempotent

Convert the hedged share at the forward rate and the remainder at settlement spot, quoted in home currency per foreign unit.

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": {
      "foreign": "<foreign>",
      "spot": "<spot>",
      "forward": "<forward>",
      "hedge": "<hedge>"
    },
    "name": "bpj_foreign_payable_hedge_blend"
  }
}

Input Schema

NameRequiredDescriptionDefault
spotYes
hedgeYes
foreignYes
forwardYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, and the description correctly stays consistent with that. It adds the computational model beyond the annotations, but says nothing about the return value, rounding/precision, or edge cases such as hedge=0 or hedge=100.

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?

A single tight sentence with no filler; the conversion rule is front-loaded and the quoting basis is appended where it is relevant.

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 four-required-parameter pure calculation with no output schema, the description covers the essential computation model and unit convention. The remaining gap is the shape of the returned value, which is a modest omission for a deterministic numeric function.

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%, so the description must carry parameter meaning. It does explain the relationship among hedge, forward, and spot (hedged share at forward, remainder at spot) and the home-per-foreign quoting basis, but it never states that hedge is a percentage of the foreign payable, nor does it clarify units of the result.

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 names a specific operation ('Convert') and resource ('hedged share', foreign payable) and states the blended-rate logic: hedged portion at forward, remainder at spot. It is clear what the tool computes, though it does not distinguish itself from any sibling by name.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The scenario (a partially hedged foreign payable) is only implied by the formula, so the agent must infer applicability.

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.