Skip to main content
Glama

veritas-8183-3star-rating-seal

quote_multitoken_escrow

Read-onlyIdempotent

[Private] Read-only price quote: how much USDC a seller receives, with fees, if the buyer uses SOL, ETH, VIRTUAL, USDT or USDC. Does not move funds. Example: tokenSymbol='SOL', tokenAmount=0.5.

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": {
      "tokenSymbol": "<tokenSymbol>",
      "tokenAmount": "<tokenAmount>"
    },
    "name": "quote_multitoken_escrow"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAmountYesAmount of input token to quote.
tokenSymbolYesInput token symbol to swap and lock.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / tokenAmount / description
      Added value: +"Amount of input token to quote."
    • addedInput schema / properties / tokenAmount / examples
      Added value: +[
      +  10
      +]
    • addedInput schema / properties / tokenSymbol / description
      Added value: +"Input token symbol to swap and lock."
    • changedInput schema / properties / tokenSymbol / enum
      Previous value: -[
      -  "SOL",
      -  "ETH",
      -  "VIRTUAL",
      -  "USDT",
      -  "USDC"
      -]New value: +[
      +  "USDC",
      +  "ETH",
      +  "SOL",
      +  "VIRTUAL",
      +  "USDT"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description still adds real context beyond them: fees are included in the quote, the payout denomination is USDC while the input can be SOL/ETH/VIRTUAL/USDT/USDC, and '[Private]' flags a visibility constraint the annotations do not express. It does not describe latency, rate limits, or quote staleness, which would be the final step to a 5.

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?

Three short sentences, front-loaded with the operation and its read-only nature, then the token universe, then a concrete example. Every sentence earns its place; the only minor redundancy is re-listing the tokens already enumerated in the schema.

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?

With no output schema, the description correctly takes on the burden of explaining the return value (USDC amount to the seller, net of fees), and both required parameters are the only inputs. What remains missing is guidance on when in the escrow lifecycle to call it and how fresh the quote is, which matters for a pricing tool but is not essential to invoke it.

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 coverage is 100% with a documented enum on tokenSymbol and a described tokenAmount, so the schema carries the semantics. The description's contribution is a worked example (tokenSymbol='SOL', tokenAmount=0.5) and a restatement of the accepted symbols, which is mildly useful but largely duplicative of the enum — baseline 3.

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 uses a specific verb+resource ('Read-only price quote' for a multitoken escrow) and states the outcome dimension explicitly: USDC received by the seller, inclusive of fees. It also names the exact input token set, so an agent can tell this is a quoting tool rather than a settlement one; it stops short of naming a sibling alternative, which keeps it at 4.

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 implied rather than stated: 'Does not move funds' plus the quote framing suggests calling it before an escrow-opening flow, but there is no explicit 'use this when / do not use this when' and no reference to any of the many audit_* or open_escrow_job siblings. An agent must infer the ordering itself.

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.