Spice MCP

Create Saved Query

dune_query_create

Create a new saved Dune query by providing a name and SQL. Requires the SPICE_DUNE_ALLOW_SAVES environment variable set to true.

Instructions

Create a new saved Dune query (name + SQL). Requires SPICE_DUNE_ALLOW_SAVES=true.

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": {
      "name": "<name>",
      "query_sql": "<query_sql>"
    },
    "name": "dune_query_create"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`query_sql`	Yes
`description`	No
`tags`	No
`parameters`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2025

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations provided, the description must disclose behavioral traits. It reveals a required environment variable, which is a critical constraint. However, it does not describe other behaviors such as whether existing queries are overwritten, if SQL validation occurs, or what the response looks like.

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 extremely concise: two sentences with no unnecessary words. Every part adds value—action, required fields, and a prerequisite.

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?

Given the lack of annotations, 0% schema coverage, and presence of an output schema, the description is incomplete. It does not explain the return value, the effect of optional parameters, or the implications of the environment variable beyond being required.

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 coverage is 0%, so the description should compensate. It mentions 'name + SQL' (covering the two required parameters), but fails to describe the three optional parameters (description, tags, parameters). The agent lacks information on their purpose or format.

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 clearly states it creates a new saved Dune query, specifying 'name + SQL'. While it doesn't explicitly differentiate from siblings like dune_query_update or dune_query_fork, the verb 'create' and mention of saving indicate a distinct purpose.

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?

The description includes a prerequisite (SPICE_DUNE_ALLOW_SAVES=true), which helps the agent know when it can be used. However, it lacks guidance on when to use this tool vs. alternatives like dune_query_update or dune_query, and does not mention any context for creation.

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

Deploy Server