Skip to main content
Glama

Aevum: verified trading records

Ask a signal seller for proof

prove_it_message
Read-only

Writes a short, polite message a buyer can send a signal seller (Discord, Telegram, X, email) asking them to lock their next calls on Aevum before the buyer pays, so wins and losses both end up on a record anyone can check. Nothing is sent or stored; return the text for the person to copy.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prove_it_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsNoHow many upcoming calls to ask for (default 3; each wallet can lock 3 per 30 days, so 5 or 10 take months)
sellerNoSeller's name or handle (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces that with "Nothing is sent or stored; return the text for the person to copy" — useful because the mention of Discord/Telegram/X could otherwise make an agent think the tool sends messages. Beyond that, it does not add rate-limit, formatting, or placeholder-handling behavior, so it adds some context without going deep.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence, front-loaded with the verb and resource, followed by a short clarifying sentence. It is efficient, though the long clause about wins and losses is somewhat run-on and competes with the core instruction.

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 no-side-effect text-generation tool with 100% schema coverage and clear annotations, the description covers purpose, timing, and return value. The only remaining gaps are minor — the exact structure or optional parts of the generated message, and any guidance on handling a missing seller handle.

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?

Schema coverage is 100% and the schema itself explains the 3/5/10 options and the 30-day lock limit per wallet. The description adds nothing about the parameters, so this is baseline territory rather than a strength.

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 description gives a specific verb and resource ("Writes a short, polite message a buyer can send a signal seller") plus the ultimate goal: getting the seller to lock future calls on Aevum so results become publicly verifiable. That is clearly distinct from siblings such as draft_call or publish_call, which act on calls rather than producing a seller-facing message.

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?

The timing and context are explicit: this is used before the buyer pays, so wins and losses end up on a checkable record. It also states the delivery channels (Discord, Telegram, X, email) and that the output is meant to be copied rather than sent. It does not name an alternative tool or an exclusion case, so it stops short of a 5.

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