Skip to main content
Glama

automaton-colony

by io.github.AutomatonColony

Buy a Flash Report (paid, x402)

buy_flash_audit

Paid over x402 in USDC on Base. Without a payment in _meta["x402/payment"] it returns the PaymentRequired document (isError). With a valid PaymentPayload it validates, settles asynchronously and returns an orderKey to collect with collect_flash_audit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
languageNoReport language. Defaults to "en".
targetAddressYesContract or B20 token address on Base mainnet (eip155:8453), 0x + 40 hex.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

It discloses important behaviors beyond annotations: the PaymentRequired error document when no payment is present, validation and asynchronous settlement, and the returned orderKey. Annotations only indicate non-read-only/open-world/non-idempotent, so this description adds substantial behavioral context.

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?

The description is compact and front-loaded with the essential payment constraint, followed by the two relevant behavioral paths. Every sentence earns its place, and the title adds clarity without redundancy.

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 paid tool with no output schema, the description covers the required payment context, the error path, the asynchronous behavior, and the handoff to collect_flash_audit. It could mention the payment amount or where to find pricing/terms, but the core calling flow is clear.

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 coverage is 100%, with the description already documenting both parameters, including the enum and pattern. The tool description adds no new parameter-level detail, so the baseline of 3 is appropriate.

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?

The description clearly identifies the action: paying over x402 in USDC on Base to buy a flash audit. It also distinguishes itself from collect_flash_audit by stating it returns an orderKey to be used with that sibling, and the title reinforces the paid nature.

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 description implies the usage sequence: send payment, get orderKey, then collect via collect_flash_audit. However, it does not explicitly state when to prefer this over check_contract_free or flash_audit_terms, leaving the choice to inference.

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

All automaton-colony toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct stage: getting payment terms, initiating a paid audit, collecting its result, or performing a free on-chain check. The overlap between flash_audit_terms and the unpaid response from buy_flash_audit is clearly explained, so an agent can reliably tell them apart.

Naming Consistency3/5

buy_flash_audit and collect_flash_audit follow a clear verb_noun pattern, but check_contract_free adds a trailing adjective and flash_audit_terms drops the verb entirely. The names are readable and descriptive, yet the conventions are mixed.

Tool Count5/5

Four tools exactly cover the server's narrow scope: one free check, plus the three-step paid audit workflow of terms, buy, and collect. No tool feels redundant and the count is well below any bloat threshold.

Completeness5/5

The free check is a self-contained operation, and the paid audit flow is complete from fetching terms to buying and polling for the delivered report. There are no obvious dead ends or missing lifecycle steps for the stated purpose.

Resources