Skip to main content
Glama
Sign In
Preflight

Preflight

by dainidude
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

preflight_check

Scan Solidity source code and return a security verdict so you can assess contract risks before deployment. Paid per call via x402; dev mode requires no payment.

Instructions

Scan Solidity source and return a security verdict. This is a paid call ($0.01 USDC on Base mainnet) that flows through x402; in dev mode (DEV_MODE=1) no payment is required.

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": {
      "source": "<source>"
    },
    "name": "preflight_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
contract_nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses that this is a paid call ($0.01 USDC on Base mainnet) routed through x402 and that DEV_MODE=1 bypasses payment. That is real behavioral context an agent needs before invoking. It stops short of covering what happens on payment failure, wallet/auth requirements, or whether the call is read-only, so it is strong but not exhaustive.

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?

Two tight sentences: purpose first, then the payment constraint. No filler, no repetition, and the cost caveat is front-loaded before the agent commits to a call.

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

Completeness3/5

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

The output schema exists, so return values need not be explained, and the payment/dev-mode behavior is well covered. However, an undocumented `contract_name` parameter and the absence of any guidance on payment failure or invocation prerequisites leave gaps for a two-parameter, paid tool.

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 description coverage is 0%, so the description must compensate. It only implies the role of `source` (the Solidity code to scan); `contract_name` is never mentioned in either the schema or the description, leaving an agent to guess its purpose and whether it is optional or affects the verdict.

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?

"Scan Solidity source and return a security verdict" gives a specific verb (scan) and resource (Solidity source) plus the output kind (security verdict). It is distinguishable from siblings like preflight_token_risk and preflight_sim by the Solidity-source scope, but the description never names those siblings or states the distinction explicitly.

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?

Usage is implied by the input type: if you have Solidity source and want a security verdict, use this. There is no explicit when-to-use versus preflight_sim or preflight_token_risk, and no stated prerequisites beyond payment mode.

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

Deploy Server

Other Tools