Skip to main content
Glama

Quote protocol fee

quote_fee
Read-onlyIdempotent

Calculates protocol fees, buyer deposits, seller receipts, and Buyer Review bonds with a 1.5% cap; optionally cross-checks on-chain fee values and flags differences without moving or signing funds.

Instructions

Calculate the protocol fee, buyer deposit, seller receipt and Buyer Review bond with the integer formula: 1.5% of the job amount, capped at 50 USDC. Does not move funds. If buyer_address is set, also read protocolFeeFor and arbitrationReserveFor and flag any difference. Does not sign or send.

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": {
      "amount_usdc": "<amount_usdc>",
      "mode": "<mode>",
      "starter": "<starter>"
    },
    "name": "quote_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
starterYes
amount_usdcYesJob amount in USDC as a decimal string with at most 6 fraction digits.
buyer_addressNoOptional checksummed buyer address for an on-chain fee cross-check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds real value on top: it clarifies no funds move and nothing is signed or sent, and that setting buyer_address triggers an on-chain read of protocolFeeFor and arbitrationReserveFor with discrepancy flagging. This explains a side-effect-adjacent behavior (external reads) that the annotations alone would not make obvious.

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?

Front-loads the formula and outputs in one dense sentence, then adds constraints. Mostly efficient, though the two trailing 'does not...' clauses are slightly fragmented and could be consolidated without losing meaning.

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?

No output schema exists, and the description does the right thing by enumerating the returned figures and the fee formula. The main remaining gap is enum semantics for mode and starter, which matter for a 3-required-parameter tool.

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?

With schema coverage at 50%, the two enum parameters (mode: automatic/buyer_review, starter: buyer/seller) carry no schema descriptions. The description indirectly explains them by naming the 'Buyer Review bond' and buyer/seller deposit and receipt outputs, but it never explicitly defines what each enum value selects, so half the parameter space remains under-explained.

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 precise verb (Calculate) and enumerates the exact quantities produced: protocol fee, buyer deposit, seller receipt and Buyer Review bond, plus the governing formula (1.5%, capped at 50 USDC). An agent can tell this is a pure computation tool, distinct from mutating siblings like prepare_deal.

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?

Usage is only implied via negations ('Does not move funds', 'Does not sign or send'), which signals a pre-flight quote step but never says when to call it versus prepare_deal or get_deal_status. No explicit prerequisites or ordering guidance is given.

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

Deploy Server

Other Tools