E3D Pilot

e3d_quote

Read-only

Returns a single-use debate price quote, including quote_id, maximum charge in credits, expiration, and key limits. Free: no credits are spent or reserved. Only a question hash and its size reach billing. The quote is valid only for identical debate arguments.

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": {
      "question": "<question>"
    },
    "name": "e3d_quote"
  }
}

Input Schema

Name	Required	Description
`mode`	No	quick (default): 1 round, short answers, no cross-critique. thorough: 2 rounds where models see and rebut each other.
`rounds`	No	Override the mode's round count. Stops early on convergence.
`experts`	No	Optional. 2 up to your panel size (at most 4) expert names from e3d_list_experts, in the order you want; send the SAME list on e3d_quote and e3d_debate. Each expert is a lens that tells one model what to look for; Pilot gives each to a different vendor, so you never choose models. Lenses add perspectives; they are not measured to improve answers. The quote shows the extra cost.
`question`	Yes	The decision or question, with enough context for models that cannot see your code.
`max_words`	No	Override the mode's per-provider per-round answer cap.
`providers`	No	Provider identifiers. Defaults to the server’s configured panel.
`web_search`	No	Let the API models (Anthropic, OpenAI, Google, xAI) search the web for current facts. Default true. false keeps the question away from search providers.
`investigate`	No	true when quoting round 1 of e3d_investigate: its verdict also writes follow-up questions, so it is priced a little higher. Omit for e3d_debate.

Output Schema

Name	Required	Description
`experts`	No	Only when you passed experts: their names and credits_without, the maximum without the lenses (max_credits includes them).
`quote_id`	Yes
`expires_at`	Yes
`key_limits`	Yes	Advisory read of the key's caps (credits; null means no such cap): cap_per_run_credits, cap_daily_credits, cap_daily_remaining_credits, cap_total_credits, cap_total_remaining_credits, service_max_per_run_credits.
`max_credits`	Yes
`ttl_seconds`	Yes
`schema_version`	Yes
`search_enabled`	No	Whether this quote includes web search.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 7, 2026

addedInput schema / properties / experts

Added value: +{
+  "description": "Optional. 2 up to your panel size (at most 4) expert names from e3d_list_experts, in the order you want; send the SAME list on e3d_quote and e3d_debate. Each expert is a lens that tells one model what to look for; Pilot gives each to a different vendor, so you never choose models. Lenses add perspectives; they are not measured to improve answers. The quote shows the extra cost.",
+  "items": {
+    "maxLength": 64,
+    "pattern": "^[a-z0-9]+(-[a-z0-9]+)*$",
+    "type": "string"
+  },
+  "maxItems": 16,
+  "minItems": 2,
+  "type": "array",
+  "uniqueItems": true
+}

addedOutput schema / properties / experts

Added value: +{
+  "description": "Only when you passed experts: their names and credits_without, the maximum without the lenses (max_credits includes them).",
+  "properties": {
+    "credits_without": {
+      "type": "integer"
+    },
+    "names": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 7, 2026

addedInput schema / properties / investigate

Added value: +{
+  "description": "true when quoting round 1 of e3d_investigate: its verdict also writes follow-up questions, so it is priced a little higher. Omit for e3d_debate.",
+  "type": "boolean"
+}

First observedOct 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, but the description adds substantial context beyond them: the call is free, nothing is spent or reserved, only a question hash and its size reach billing, and the resulting quote expires and is bound to identical arguments. It does not say what error or behavior results if the arguments differ from the quote, which is the one operational gap.

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?

Four short sentences, each carrying distinct information: what is returned, cost, privacy/billing scope, and validity constraint. The most decision-relevant fact (free) is front-loaded after the purpose sentence, with no padding.

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 an output schema present, the description need not detail return fields, yet it still summarizes them usefully. The essential quote-then-debate coupling is stated; the minor omission is what happens when debate arguments deviate from the quoted ones.

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%, so every parameter is already documented in the schema, including mode, rounds, experts, and investigate. The description only references a 'question hash' and never clarifies parameter semantics, so the baseline of 3 applies.

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 opens with a specific verb and resource ('Returns a single-use debate price quote') and enumerates what the quote contains (quote_id, maximum charge in credits, expiration, limits). It is clearly distinct from e3d_debate or e3d_investigate, though it never names a sibling explicitly to route the agent.

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 when-to-use is implied rather than stated: 'single-use' plus 'valid only for identical debate arguments' signals that this precedes a debate call with matching arguments. It never says 'call this before e3d_debate' outright and gives no when-not-to-use condition.

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

All E3D Pilot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?