Skip to main content
Glama

Vino & Views

by io.github.oriondrayke
OverviewDiscussionsAdmin

tx_preflight

Read-onlyIdempotent

Free. Unsigned EVM eth_call and gas estimate at a measured block; flags approvals and delegated target code. Never signs or broadcasts.

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / max_charge_atomic
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Max Charge Atomic"
-}
    • removedInput schema / properties / operation_id
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Operation Id"
-}
  2. Changed1 schema field changed
    • addedInput schema / properties / operation_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Operation Id"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / max_charge_atomic
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Max Charge Atomic"
+}
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value beyond them: it simulates at a measured block, flags approvals and delegated target code (e.g. EIP-7702), and guarantees it never signs or broadcasts. Missing only details like rate limits or failure handling.

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?

Three tight clauses with zero waste, front-loaded with 'Free.' and followed by the mechanism and the safety guarantee. Every sentence carries distinct information.

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?

For a simulation tool with no output schema, the description covers the essential behavior (eth_call, gas estimate, approval/delegation flags) and the safety profile, which annotations reinforce. A hint about the returned result shape would make it fully self-sufficient, but the core is present.

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?

The single top-level 'request' parameter has no description and overall schema description coverage is 0%, so the description must compensate but adds nothing about chain, sender, target, data, or value_wei. It neither explains the request object's shape nor the meaning of fields the schema leaves undocumented.

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?

States a specific verb and resource: unsigned EVM eth_call plus gas estimate, explicitly scoped to a preflight simulation rather than a real submission. The additional clause about flagging approvals and delegated target code sharpens what the tool actually produces. No sibling tool (all payment/escrow oriented) overlaps, so no differentiation is needed.

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?

'Free' and 'Never signs or broadcasts' imply this is the safe dry-run to call before a real transaction, but the description never states when to use it versus alternatives or names any prerequisite. Usage must be inferred from the framing rather than read explicitly.

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

All Vino & Views toolsInspect
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