Skip to main content
Glama
Sign In

Flow — Order-Flow Intelligence on Base

by io.github.flow-executor
OverviewDiscussionsAdmin

flow_paycheck

Before you pay this agent, check. PayCheck ($0.50 USDC via x402 on Base) runs Flow's whole checker stack on a payee in ONE call — the payee verdict (kind, on-chain activity, the full contract-safety engine when the payee is a contract), the wallet approval-exposure audit, contract safety, and the payee's recent USDC settlement history — and returns one finished grade (ALLOW / REVIEW / BLOCK with a 0-100 score), a verify_status (verified / failed / unverified_verifier_down), every check, the evidence under it, and a receipt. The guarantee: the report is produced before settlement; if it cannot be produced, the payment is never settled — no report, no charge. This hosted endpoint does not hold a wallet: an unpaid call returns the endpoint's x402 payment challenge itself, never an invented result. Pay it with any x402 client, or use the @flowexecutor/flow-mcp stdio package with an Early Builder Key.

Input Schema

NameRequiredDescriptionDefault
payeeYesThe payee address to grade before paying (0x…), Base

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / amountUsd
      Removed value: -{
-  "description": "Optional: the intended payment amount in USD (> 0, up to 100). Declaring it attaches Flow Promise coverage to the receipt.",
-  "type": "number"
-}
  2. Changed1 schema field changed
    • addedInput schema / properties / amountUsd
      Added value: +{
+  "description": "Optional: the intended payment amount in USD (> 0, up to 100). Declaring it attaches Flow Promise coverage to the receipt.",
+  "type": "number"
+}
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the $0.50 USDC cost via x402 on Base, the no-wallet hosted model, that an unpaid call returns the x402 challenge rather than a fabricated result, and the no-report-no-charge guarantee tied to pre-settlement production.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical trigger is front-loaded in a short first sentence, followed by dense but purposeful detail about cost, output, guarantees, and invocation. It is on the long side with several run-on clauses, but nearly every clause conveys decision-relevant information.

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

Completeness5/5

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

There is no output schema, yet the description compensates by enumerating the return shape (grade with score, verify_status values, per-check evidence, receipt) and the payment failure mode. An agent has everything needed to decide and invoke correctly.

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?

Only one parameter, and the schema already documents it at 100% coverage including the 0x format and Base chain context. The description reinforces the meaning ('the payee address to grade before paying') but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 — running Flow's checker stack on a payee in one call — and enumerates exactly what is produced (verdict, verify_status, checks, evidence, receipt). An agent can distinguish this from flow_health and flow_quote without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The opening 'Before you pay this agent, check' establishes the triggering context clearly, and the closing sentence names two concrete invocation paths (any x402 client, or the stdio package with an Early Builder Key). It stops short of naming a when-not condition or contrasting against the sibling tools directly.

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

All Flow — Order-Flow Intelligence on Base 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