Skip to main content
Glama

falcon.sol structures

price_note

falcon.sol structures: structured-note pricing for crypto. Send a JSON term sheet (autocallable, barrier reverse convertible, range accrual, principal-protected, shark fin) on BTC, ETH or SOL; get the fair coupon or participation, probabilities (autocall per observation, knock-in, loss), greeks, a spot x vol scenario grid and payoff-diagram data. Monte Carlo on live Deribit implied vol. Free preview; full quote $0.02 USDC via x402 on Solana or Base. Costs $0.02 USDC (x402).

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": {
      "termSheet": "<termSheet>"
    },
    "name": "price_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
termSheetYesTerm sheet JSON; see /schema/term-sheet.json. Example: {"underlying":"ETH","notionalUsd":10000,"issuerMarginBpsPa":200,"product":{"type":"autocallable","tenorDays":30,"obsFreqDays":7,"autocallBarrier":1,"couponBarrier":0.8,"knockInBarrier":0.7,"memory":true,"nonCallDays":0},"market":{},"seed":20261023}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does useful work: it discloses Monte Carlo pricing on live Deribit implied vol, the delivered outputs, free preview versus paid full quote, x402 payment on Solana/Base, and the $0.02 USDC cost. It stops short of explicitly stating side-effect/read-only status, rate limits, or error behavior.

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?

The description front-loads the core purpose and efficiently packs in product scope, outputs, pricing method, and payment model. The final sentence repeats the $0.02 USDC x402 cost already stated earlier, which is a minor redundancy but does not undermine the otherwise dense structure.

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 complex pricing tool with no output schema and no annotations, the description covers the product universe, output metrics, pricing methodology, payment model, and input pointer. It is strong overall, though it lacks explicit return-shape, latency, or error-behavior details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter and the schema coverage is 100%, with the nested termSheet object documented by pointer and example. The description adds value beyond the schema by listing supported product types (autocallable, barrier reverse convertible, range accrual, principal-protected, shark fin) and supported underlyings BTC, ETH, or SOL.

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?

Names a specific resource and operation: structured-note pricing for crypto via a JSON term sheet, returning fair coupon/participation, probabilities, greeks, scenario grid, and payoff data. It also enumerates supported products and underlyings, making clear it is a pricing engine rather than a generic market snapshot or simple preview.

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?

Explains the input expectation (send a term sheet) and distinguishes a free preview from a paid full quote with cost details. However, it never names the sibling preview_note or explicitly says when to use this tool versus that one; routing guidance is only implied by the word 'preview' and the price.

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.

Resources