Skip to main content
Glama

WLFI buyback tracker: how much World Liberty has bought, the pace and the days left

get_wlfi_buyback
Read-only

The World Liberty Financial WLFI buyback (announced 06-11-2026, buying began 09-11-2026 with 10,000,000 USD1 put on Aster), read by OwlChart from the Aster WLFI/USD1 spot pair (v5.888): bought so far (estimated from taker buys above the baseline of the ten days before), percent of the 10,000,000 USD1 used, pace per day over the last 7 days, days left at that pace and the date it lasts until, the flow of the last 24 hours, the size and rhythm of the buy orders, the flow by day with the WLFI close, the WLFI price since the announcement and since the start, and what World Liberty has published (wallet, total budget, burn or hold: null until published). An estimate from public exchange data, never a World Liberty figure. Page: owlchart.com/wlfi.html.

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": "get_wlfi_buyback"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower, and the description still adds real behavioral context: the figures are an estimate derived from taker buys above a ten-day pre-buyback baseline on the Aster WLFI/USD1 spot pair (v5.888), and certain published fields are null until World Liberty releases them. It explicitly warns the numbers are never an official World Liberty figure, which is exactly the kind of provenance caveat an agent needs.

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?

The whole definition is a single very long run-on sentence in which announcement dates and the Aster pair/version come before the list of returned fields, delaying the payload. Every clause does carry information, but the comma-chained field listing is hard to scan and would read far better as a short lead plus a bulleted field list.

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 input schema, no output schema, and simple read-only annotations, the description carries the burden of saying what comes back, and it does so field by field, plus source, estimation method, null semantics, and a documentation page link. The main remaining gap is absence of any note on freshness or update cadence, which matters for a live flow tracker.

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 tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description instead spends its words on output content and data provenance, which is the right allocation for a zero-argument call.

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 names a specific resource (the WLFI buyback by World Liberty Financial) and enumerates exactly what the tool returns: amount bought, percent of the 10,000,000 USD1 budget used, pace per day, days left, 24h flow, order sizes, daily flow with close, price since announcement/start, and published figures. An agent can tell instantly this is the WLFI-buyback snapshot tool and that no sibling covers that subject.

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: the content list makes clear it answers questions about WLFI buyback progress, pace, and remaining days. There is no explicit when-to-use/when-not statement, no mention of alternatives such as get_token_hub or get_price_history for broader WLFI pricing, and no mention of refresh cadence or rate limits for repeated polling.

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