Skip to main content
Glama
Sign In
valorem-mev-mcp

valorem-mev-mcp

Official
by ValoremFoundation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

decoded_hints

Retrieve the last 50 decoded Flashbots MEV-Share hints, including swap direction, pool address, and token pair, for front-running detection and MEV opportunity scanning.

Instructions

Returns the last 50 decoded MEV-Share hints from the Flashbots hint stream. Each hint includes swap direction (buy/sell), pool address, and token pair. Useful for front-running detection and MEV opportunity scanning. Cost: $0.10 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses important behavioral traits: call limit (last 50), output structure (swap direction, pool address, token pair), and cost ($0.10 USDC per call). It does not mention authentication or rate limits, but the disclosed cost and data details provide significant transparency.

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 three sentences, front-loaded with the main action, then provides useful detail and cost. Every sentence earns its place with no fluff or repetition.

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?

Given no output schema, the description adequately describes what the tool returns and what each hint contains, plus cost and use cases. This is sufficient for an agent to understand the tool's functionality and justify invocation.

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 has zero parameters, and schema coverage is 100%, so the description does not need to explain parameters. It instead describes the output, which is appropriate given the empty input schema.

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 returns the last 50 decoded MEV-Share hints, with a specific action (returns), resource (hints from Flashbots stream), and detail (last 50). It distinguishes itself from sibling tools by mentioning MEV-Share hints, which no other sibling tool does.

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 a clear use case: 'Useful for front-running detection and MEV opportunity scanning.' This gives context for when the tool would be relevant, though it does not explicitly mention when not to use it or name alternatives.

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

Deploy Server

Other Tools