Skip to main content
Glama
Diogenes Web3, DeFi & HTTP 402 Security MCP

Diogenes Web3, DeFi & HTTP 402 Security MCP

mev_risk

Evaluate MEV sandwich and frontrunning risk before a swap, then return recommended slippage in basis points for the DEX token pair.

Instructions

Pre-swap MEV sandwich and frontrunning risk evaluator returning optimal slippage in basis points.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dex": "<dex>",
      "token_in": "<token_in>",
      "token_out": "<token_out>"
    },
    "name": "mev_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
dexYes
token_inYes
token_outYes
slippage_bpsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the output conceptually ('optimal slippage in basis points') and implies a read/evaluation operation with no mutation, which is meaningful beyond structured data. It omits permissions, latency, determinism, and any side-effect profile, leaving notable gaps.

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

Conciseness4/5

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

A single dense sentence with the evaluative purpose and the output value front-loaded, and no wasted clauses. It is efficiently sized for a one-line tool description.

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

Completeness2/5

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

With no output schema and no annotations, the description should explain what the evaluation actually returns besides a slippage figure (e.g., a risk score or sandwich warning), and it should document the required token/dex inputs. As written, an agent could call it but would not know the full response shape or how to interpret a risk result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across all four parameters, so the description must compensate. It hints at slippage_bps via 'slippage in basis points' but gives no meaning for dex, token_in, or token_out, which are the three required inputs. Coverage of parameter semantics is well short of what a 0%-coverage schema demands.

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 names a specific verb-and-resource pair: a pre-swap MEV sandwich and frontrunning evaluator. It clearly scopes the tool's domain (MEV risk ahead of a swap), which an agent can distinguish from audit-oriented siblings like contract_audit or solana_risk. It stops short of explicitly contrasting itself with any named sibling, so a 4 rather than a 5.

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?

'Pre-swap' signals the timing context (call before executing a swap), which is useful implied guidance. However, there is no explicit statement of when-not to use it, what alternatives exist, or prerequisites for interpreting the result. Usage is inferable but not spelled out.

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