Skip to main content
Glama
minia2auk

minia2a-mcp

Official
by minia2auk
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

minia2a_call_service

Destructive

Call x402 services on minia2a.uk with free trial credits or automatic USDC micropayments. Use your private key to sign trial calls or enable autoPay to settle 402 responses and retry.

Instructions

Call an x402 service on minia2a.uk. Three access paths: (1) omit everything for the paid 402 path (register a wallet for 5 free trial calls); (2) pass privateKey (or set MINIA2A_PRIVATE_KEY) for your registered wallet's own 5 trials — the key never leaves this process, it only signs the per-call trial message; (3) when both are exhausted the endpoint returns HTTP 402 with a machine-readable accepts[] array — pay in USDC and retry with a PAYMENT-SIGNATURE header (x402 V2). Set autoPay:true together with privateKey to have a 402 paid automatically in USDC on Base and the call retried — the wallet must hold USDC or the call still returns payment_required (never charges silently). Note that wallet= on its own does NOT reach the wallet bucket; the signature is what does.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNoJSON parameters to send to the service
walletNoYour registered self-custody wallet address (0x...). Without privateKey this alone does not draw on the wallet's trial bucket.
autoPayNoWhen true and a privateKey is available, a 402 Payment Required response is paid automatically in USDC on Base via x402 and the call retried. Default false — you get a payment_required response instead of any automatic charge. Empty wallet (no USDC) still returns payment_required.
serviceIdYesThe service ID (e.g., 'x402-gas') or full endpoint path
privateKeyNoPrivate key of the registered wallet, used locally to sign the trial message (EIP-191). Never transmitted — only the resulting signature is sent. Falls back to the MINIA2A_PRIVATE_KEY env var.

Schema Changelog

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

  1. First observedv1.0.0

TDQS

A5/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses real behavioral details: the private key never leaves the process, only the signature is transmitted, automatic payment never silently charges, and a 402 response triggers manual or automatic payment handling. No contradiction with the annotations exists.

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 dense but well-structured with numbered access paths, followed by the autoPay caveat and a critical final note about wallet. Every sentence earns its place and there is no repetition of the schema.

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?

The tool has a complex payment/trial model, and the description fully covers trial buckets, 402 handling, automatic payment, security, and failure conditions. A generic success return format cannot be defined since output depends on the called service, but the x402 flow is well specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, and the description adds essential meaning beyond the schema: the privateKey is used locally for EIP-191 signing, autoPay requires privateKey and USDC, and wallet alone does not access the wallet trial bucket. These details materially affect how parameters must be combined.

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 opens with a specific verb and resource: 'Call an x402 service on minia2a.uk', then explains three distinct access paths. This clearly separates it from sibling metadata, registration, and stats tools.

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

Usage Guidelines5/5

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

It gives explicit guidance on exactly when to use each mode: omit everything for the paid path, pass privateKey for trial calls, and enable autoPay with privateKey for automatic 402 payment. It also states an important exclusion: wallet alone does NOT reach the wallet bucket.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/minia2auk/minia2a-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server