Skip to main content
Glama

validity_build

Read-onlyIdempotent

Make any signed Base transaction conditional (Cobalt) — Make any signed Base transaction conditional (Cobalt validity tx): Base includes it only while your conditions hold. We validate the predicates and return the base_sendRawTransactionValidity request; we never touch funds or keys. Every request carries the deadline Base requires (at most 60 s out; set for you if omitted). Optional conditions: fromBlock, minNativeBalanceWei, or a storage predicate for price. Priced $0.01 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.

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

Input Schema

NameRequiredDescriptionDefault
signedTxNoYour signed serialized tx (optional)
fromBlockNoEarliest block (optional)
storageOpNoAdvanced: operator (< <= = != > >=)
beforeBlockNoDeadline block (optional; at most 60 s out, set for you if omitted)
storageMaskNoAdvanced: mask (hex, optional)
storageSlotNoAdvanced: storage slot (hex)
storageValueNoAdvanced: compare value (hex)
balanceAddressNoAccount for the balance floor (optional)
storageAddressNoAdvanced: pool/token for a storage condition
minNativeBalanceWeiNoMin ETH balance floor, wei (optional)

Output Schema

NameRequiredDescriptionDefault
dataNoThe result payload. Shape is service-specific; every field is documented in the tool description.
serviceNoThe service id that answered.
checkedAtNoISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / flashblockIndex
      Removed value: -{
      -  "description": "Flashblock index 1-10 (optional)",
      -  "type": "string"
      -}
    • removedInput schema / properties / flashblockIndexOp
      Removed value: -{
      -  "description": "Flashblock operator (optional, default =)",
      -  "type": "string"
      -}
  2. Changed2 schema fields changed
    • changedInput schema / properties / beforeBlock / description
      Previous value: -"Deadline: before this block (recommended)"New value: +"Deadline block (optional; at most 60 s out, set for you if omitted)"
    • changedInput schema / properties / flashblockIndex / description
      Previous value: -"Flashblock index (optional)"New value: +"Flashblock index 1-10 (optional)"
  3. Added

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses that the tool validates predicates and returns a raw request without touching funds or keys, that the deadline is capped at 60 s and auto-filled if omitted, and it spells out pricing, free-tier and auth mechanics. That is exactly the behavioral context an agent needs.

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 core purpose is front-loaded and the important constraints follow in a logical order. However, the opening phrase is literally repeated twice ('Make any signed Base transaction conditional (Cobalt) — Make any signed Base transaction conditional (Cobalt validity tx)'), which is wasted space in an otherwise tight description.

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, return values need not be explained, and the description still names the returned request type. For a 10-parameter tool it covers the deadline rule, auth, cost and safety posture well, leaving only the advanced storage sub-fields to the schema.

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?

Schema coverage is already 100%, so the baseline is 3. The description earns above that by grouping the parameters into meaningful concepts (optional conditions: fromBlock, minNativeBalanceWei, or a storage predicate for price) and by explaining the auto-default deadline behavior for beforeBlock, which the schema does not state.

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 states a specific verb and object: it turns a signed Base transaction into a conditional (Cobalt validity) transaction and returns a base_sendRawTransactionValidity request. The purpose is unambiguous, though it never differentiates itself from the sibling base_swap_validity, which an agent might reasonably confuse with it.

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?

It gives useful context about the inputs (a signed tx is optional, conditions are optional) and the 60 s deadline constraint, which implies when the tool applies. It never states when NOT to use it or points to base_swap_validity as the alternative, so selection guidance is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources