EVUUN

Preview Rebate Conversion

evuun_preview_rebate_conversion

Read-onlyIdempotent

Show how much of another currency’s rebate offsets this order, at Stripe’s current base rate rounded down, with the quote ID to confirm. Reserves nothing; confirm with evuun_apply_rebate and that fx_quote_id within ten minutes.

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": {
      "order_id": "<order_id>",
      "amount_minor": "<amount_minor>",
      "currency": "<currency>"
    },
    "name": "evuun_preview_rebate_conversion"
  }
}

Input Schema

Name	Required	Description	Default
`currency`	Yes
`order_id`	Yes
`amount_minor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds context annotations cannot express: conversion uses Stripe's current base rate, the result is rounded down, nothing is reserved, and the quote expires after ten minutes. The TTL and no-reservation notes are exactly the behavioral facts an agent needs before deciding to preview.

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?

Two dense sentences with no filler; the rate/rounding behavior is front-loaded and the confirmation routing follows immediately.

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 read-only preview with no output schema, the description covers what is returned (an offset amount plus a quote ID) and the validity window. The one substantive gap is that it does not clarify the semantics of the required amount argument, which matters because there is no schema documentation for it.

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 carry the parameter burden, but it only implicitly gestures at the currency ('another currency's rebate') and order ('this order'). It never explains what amount_minor represents — whether it is minor units, which currency it is denominated in — leaving the most error-prone argument undocumented.

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?

States a specific verb and resource — previewing how much of another currency's rebate offsets an order — plus the rate source and rounding behavior. It also implicitly separates itself from the mutating sibling evuun_apply_rebate, so an agent can distinguish preview from commit without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: this call reserves nothing, and confirmation happens via evuun_apply_rebate with the returned fx_quote_id within ten minutes. That is clear when-to-use and what-to-do-next guidance, though it never states a condition under which previewing should be skipped.

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

All EVUUN tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?