Spice MCP

Run Dune Query

dune_query

Execute queries on Dune Analytics to retrieve blockchain data and return an agent-optimized preview.

Instructions

Execute Dune queries and return agent-optimized preview.

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": {
      "query": "<query>"
    },
    "name": "dune_query"
  }
}

Input Schema

Name	Required	Default
`query`	Yes
`parameters`	No
`refresh`	No
`max_age`	No
`limit`	No
`offset`	No
`sample_count`	No
`sort_by`	No
`columns`	No
`format`	No	preview
`extras`	No
`timeout_seconds`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2025

TDQS

C2.6/5.0

Behavior2/5

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

No annotations provided, so the description must carry the burden. It says 'Execute' but does not disclose whether the tool is read-only, can cause side effects, requires authentication, or has rate limits. The presence of a 'refresh' parameter implies caching behavior, but this is not explained.

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

Conciseness3/5

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

The description is a single sentence, which is concise but overly terse given the tool's complexity. There is no structure (e.g., bullet points or sections) to aid readability, and it omits necessary details.

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

Completeness1/5

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

With 12 parameters, 0% schema coverage, no annotations, and a minimal description, the tool definition is severely inadequate. The agent lacks essential information to use the tool correctly, despite the existence of an output schema.

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

Parameters1/5

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

Schema description coverage is 0%, meaning none of the 12 parameters have descriptions in the schema. The tool description adds no parameter semantics—it only says 'Execute Dune queries' and 'return preview', leaving the agent without any understanding of parameters like query, parameters, refresh, limit, offset, etc.

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?

Description clearly states 'Execute Dune queries' and 'return agent-optimized preview', providing a distinct verb and resource. Among siblings like dune_describe_table or dune_query_archive, this tool's role as the execution tool is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs. alternatives (e.g., dune_query_create, dune_query_archive). The agent receives no context about prerequisites, typical use cases, or exclusions.

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

Deploy Server