clawton-agentos
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RPC_URL | No | RPC URL for Ethereum Sepolia, used for onchain audit logging. If not set, onchain logging is skipped. | |
| PRIVATE_KEY | No | Private key for a funded Sepolia wallet, used for onchain audit logging. If not set, onchain logging is skipped. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_trade_intentA | Evaluates a proposed Binance trade against a per-transaction spend cap and a rolling daily cumulative spend cap before it is forwarded to the official Binance MCP server for execution. Call this BEFORE calling any Binance MCP trading tool. |
| check_payment_intentA | Evaluates a proposed x402 protocol payment against a per-transaction spend cap and a rolling daily cumulative spend cap, shared with trade intents. Call this BEFORE signing or sending any x402 payment. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are cleanly separated by intent type: one evaluates x402 payments and the other evaluates Binance trades. Their names and descriptions make the correct choice obvious, with no functional overlap despite both being pre-flight checks.
Both tools follow the same check_<intent> convention: check_payment_intent and check_trade_intent. The pattern is predictable and makes the set easy to navigate.
Two tools is slightly below the typical 3-15 range, but the server appears intentionally scoped to guardrail checks for two specific intent types. Each tool earns its place and there is no redundant surface.
For the stated purpose of payment and trade safety checks, the server covers both target intents. It lacks any cap-management or status tools, but those may be intentionally external and agents can proceed with the checks provided.