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

valorem-mev-mcp

Official
by ValoremFoundation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

catalog

Retrieve the full Valorem MEV Intelligence service listing, including all endpoints, prices in USDC, and brief descriptions. Free to use with no payment required.

Instructions

Returns the full Valorem MEV Intelligence service catalog — all available endpoints, their prices (USDC), and brief descriptions. This tool is free and requires no payment.

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

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 of transparency. It explicitly states the tool is free and requires no payment, and it describes the returned content. It does not mention rate limits or read-only status, but for a simple catalog tool, this is sufficient disclosure.

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 two sentences long, front-loaded with the main action, and contains no unnecessary words. It efficiently conveys the purpose and key cost information.

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?

The tool is simple with no parameters and no output schema. The description covers the purpose, the specific contents of the return value, and the cost structure. This is complete for the tool's low complexity.

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, so the baseline is 4. The description adds no parameter details because none exist, and the empty schema is adequate. No further explanation is needed.

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: returning the full Valorem MEV Intelligence service catalog with endpoints, prices, and descriptions. This specific verb+resource combination distinguishes it from the sibling tools, which are individual services rather than an overview.

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 implies the tool should be used to discover available endpoints and pricing. It clearly provides context for when to use it, though it does not explicitly compare it to alternatives or state when not to use it. The free/no-payment note adds practical guidance.

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