Skip to main content
Glama

Aevum: verified trading records

Draft a call to lock

draft_call
Read-only

Prepare a market call. Always returns a link where a person reviews and locks it in their own wallet (Aevum never signs for anyone). If address is given, also returns the exact call text and unsigned Ethereum transactions, for an agent that signs with its own wallet and then calls publish_call. Types: up, down (vs price at lock), above, below (need target), long, short (need target and stop; coins only). sym: BTC, any Coinbase USD coin (ETH, SOL...), or a Kraken tokenized stock like NVDAx. days: 7, 14, 30, 60, 90.

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": {
      "type": "<type>",
      "days": "<days>"
    },
    "name": "draft_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
symNoAsset symbol, e.g. BTC, ETH, SOL, NVDAxBTC
daysYes
stopNoUSD stop price (long/short)
typeYes
reasonNoOne-line reason, max 280 characters (part of the locked text)
targetNoUSD target price (above/below/long/short)
addressNoOptional: the wallet that will sign the lock (for agents with their own wallet)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses the key behavioral guarantee ('Aevum never signs for anyone') and precisely what is returned in each case — always a review link, plus call text and unsigned transactions when `address` is set. With no output schema present, that return-path disclosure carries real weight and prevents an agent from assuming the tool signs or publishes.

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?

It is front-loaded and ordered well: purpose, then the always-true behavior, then the address path, then per-parameter notes. The trailing enum/symbol/days list is dense and telegraphic ('Types: ... sym: ... days: ...') but every fragment carries constraint information an agent needs, so there is little genuine waste.

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 7-parameter tool with no output schema, the description covers returns, signing boundaries, and the cross-parameter rules that determine a valid call. Only secondary details are absent, such as behavior when an invalid combination is supplied (e.g. long/short with a tokenized stock) or what the returned link looks like.

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?

The description adds meaning the schema does not: the valid symbol universe (BTC default, any Coinbase USD coin, Kraken tokenized stocks like NVDAx), the conditional parameter dependencies (above/below need target; long/short need target and stop; long/short are coins only), and the allowed days values. Remaining gaps are minor — `reason` is left to the schema, and stop/target units are only implied by the schema's own descriptions.

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?

The opening sentence states a specific verb and resource ('Prepare a market call'), and the description immediately distinguishes the two output paths: a human review/lock link by default, and call text plus unsigned Ethereum transactions when `address` is supplied. That routing makes it distinguishable from the sibling publish_call, which is explicitly named as the follow-on step.

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?

It clearly frames the two usage contexts: default (person reviews and locks in their own wallet) and agent-with-own-wallet (pass `address`, sign, then call publish_call). It also states a hard applicability rule (long/short are coins only). It stops short of naming explicit exclusions or error conditions, so it is strong context rather than complete when/when-not guidance.

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