Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official
by Coinversaa

Builder Heatmap

builder_heatmap
Read-onlyIdempotent

Reveal a builder's trading volume, fees, and fills across every hour and weekday over the trailing 12 weeks, identifying peak activity times and whether patterns look bot-driven or human.

Instructions

When a builder's attributed flow actually trades (takes only the 0x-hex builder address — no other parameters): a 7x24 weekday-by-hour grid as days[], always 7 entries Sunday first with weekday 0 = Sunday through 6 = Saturday, each carrying hours[], always 24 entries with hour 0 first, and every cell reporting hour, volumeUsd, feesUsd and fills totalled over the whole window; zero-activity cells are zero-valued, never omitted. No period parameter and no per-week averaging — windowDays is fixed at 84, the trailing 12 weeks, so every weekday is sampled exactly 12 times — and both weekday and hour are UTC, never local time. Attributed fills slightly undercount versus ledger revenue (trigger-order stop/TP fills not yet attributed — see the response's dataNotes). Use for 'what hours does builder X's volume peak, is it bot-like around the clock or human trading hours, and when is it safe to ship?'. Requires Pro tier. The first call for a builder can take up to ~90 seconds while the API computes it; the result is then cached, so repeat the call if it times out.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
builderYesBuilder address (0x...)
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.11.1

TDQS

A4.1/5.0
Behavior5/5

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

The description goes well beyond the annotations, disclosing that zero-activity cells are zero-valued and never omitted, that weekdays and hours are UTC, that the window is fixed at 84 days, that attributed fills undercount ledger revenue, that Pro tier is required, and that the first call can take ~90 seconds and should be retried on timeout. This is rich, actionable behavioral context with no contradiction against the readOnly/idempotent hints.

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?

Every sentence carries meaningful information, and there is no filler, but the first sentence is a very long run-on that buries the main purpose under output-shape details. Better front-loading—e.g., a direct 'Returns a 7x24 grid for a builder's attributed trades'—would make the description easier for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema present, the description fully compensates by specifying the exact shape of days[] and hours[], the cell fields, zero-value behavior, UTC semantics, the fixed window, known undercounting, access tier, and performance/caching behavior. An agent has everything needed to invoke the tool and interpret its response correctly.

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 both builder and useToonFormat already documented. The description adds useful clarifications such as 'no period parameter' and the fixed 84-day window, but it does not substantially improve parameter understanding beyond what the schema already provides, so the baseline of 3 is appropriate.

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 clearly identifies the resource (a builder's attributed flow) and the core deliverable: a 7x24 weekday-by-hour grid of volume, fees, and fills. It lacks an explicit verb like 'returns' or 'computes,' starting instead with a 'When...' clause, but the intended function is unmistakable and distinct from sibling heatmap tools.

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 description gives concrete use cases: determining when a builder's volume peaks, whether activity is bot-like, and when it is safe to ship. It does not explicitly name alternatives or say when not to use this tool, but the use-case framing plus the fixed-window/UTC constraints give an agent enough context to select it appropriately.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Coinversaa/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server