Skip to main content
Glama

MEV detection

mev_detection
Read-only

Detect MEV activity on Solana. In 'landscape' mode: returns current Jito tip floor, MEV activity level, and protection recommendations. In 'analyze' mode: checks if a specific transaction was part of a Jito bundle with tip detection and risk assessment. Costs $0.005 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": "mev_detection"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoMode: 'landscape' (general MEV overview) or 'analyze' (specific tx)landscape
transactionNoTransaction signature to analyze (required for 'analyze' mode)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description goes beyond them by disclosing the per-call cost ($0.005 USDC) and enumerating what each mode returns (tip floor, activity level, bundle membership, risk assessment). It does not mention failure behavior for an unparseable or non-existent signature.

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?

Three front-loaded sentences with no filler: purpose first, then per-mode behavior, then cost last where it belongs. Every clause carries information an agent needs before calling.

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 only two optional parameters and no output schema, the description does the work of explaining return shape per mode and surfaces the cost, which is what an agent would otherwise have to discover. The remaining gap is edge-case behavior (invalid signature, empty tip data), minor for this complexity level.

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 description coverage is 100% and the schema already states the mode enum values and that transaction is required for 'analyze'. The description restates those same mode semantics rather than adding format details (e.g., what a valid signature looks like or what happens if transaction is omitted). Baseline 3 for a fully documented schema.

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?

Names a specific verb and resource ('Detect MEV activity on Solana') and breaks the tool into two named modes with the distinct return of each spelled out, so the agent knows exactly what it gets. It does not explicitly distinguish itself from near-neighbors in the sibling list such as transaction_parse or priority_fee, which overlap with the 'analyze' path.

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?

'In landscape mode: ... In analyze mode: ...' gives concrete conditions for choosing each mode, and notes the transaction parameter is for analyze. There are no explicit exclusions or pointers to alternative tools when the user wants raw transaction decoding or priority-fee estimation.

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