Skip to main content
Glama

PreFlyte — DeFi Financial Intelligence for AI Agents

by xyz.preflyte

gas_timing

Tell agents whether now is a good or bad time to transact, based on
historical gas patterns.

Compares current gas to 24-hour and 7-day averages, identifies the
cheapest hours of the day, and estimates reference transaction costs.

Args:
    api_key: Your PreFlyte API key (required).
    chain: Chain name — "ethereum" or "arbitrum".

Returns:
    Dictionary with current gas, 24h/7d context, timing assessment
    with cheapest hours, and reference transaction costs in USD.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYes
api_keyYes

Schema Changelog

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

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains that the tool compares current gas to 24h/7d averages, identifies cheapest hours, and estimates transaction costs. It also describes the return value structure. This goes beyond the schema by detailing the computation logic, although it does not mention any side effects or permissions.

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

Conciseness5/5

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

The description is concise and well-structured, with separate sections for behavior, args, and returns. Each sentence provides necessary information without redundancy, and the format is easy to scan.

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?

For a tool with only two parameters and no output schema, the description covers all essential aspects: behavior, inputs, and output. It explicitly states what the return dictionary contains, which substitutes for a missing output schema. No critical details are omitted.

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 input schema has 0% description coverage, so the description compensates by explaining that 'api_key' is a PreFlyte API key (required) and 'chain' is either 'ethereum' or 'arbitrum'. This adds meaning beyond the schema's bare labels 'Api Key' and 'Chain'. It could be more specific about where to obtain the key, but the essential semantics are present.

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 clearly states the tool's function: telling agents whether now is a good or bad time to transact based on historical gas patterns. It uses a specific verb ('tell') and resource ('gas timing'), and distinguishes itself from sibling tools by focusing on transaction timing rather than market opportunities.

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 provides clear context for when to use the tool (when assessing transaction timing) and what data it uses (historical gas patterns). It does not explicitly mention when not to use it or name alternative tools, but the context is sufficiently clear for an agent to select it for gas-related timing decisions.

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

All PreFlyte — DeFi Financial Intelligence for AI Agents toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool serves a distinct function: assess_opportunity is a holistic decision-maker, check_entry_viability and check_pool_viability target different domains (lending vs. DEX), and estimate_net_position provides a projection unlike get_market_snapshot's current state. Even overlapping tools like get_ranking and get_returns are differentiated by their output format and filtering.

Naming Consistency4/5

Most tools follow a verb_noun pattern (assess_opportunity, estimate_net_position, verify_claim) or verb_phrase (check_entry_viability, get_market_snapshot). The outlier is gas_timing, which uses a noun_gerund structure instead of starting with a verb, breaking the otherwise consistent convention.

Tool Count5/5

With 9 tools, the server is well-scoped for a DeFi intelligence platform. Each tool covers a distinct aspect—opportunity assessment, viability checks, projections, market snapshots, historical data, gas guidance, and claim verification—without unnecessary redundancy or bloat.

Completeness4/5

The tool surface covers core decision workflows: assess, check, estimate, snapshot, ranking, history, gas, and verification. Minor gaps include lack of a tool to list supported assets/protocols/chains and no swap projection tool to complement check_pool_viability, but agents can work around these.

Resources