Genexxis paid agent tools (x402)

cloudprice_compute

Cheapest AWS EC2 instances (Linux) with at least the given vCPU and memory, on-demand or spot, optionally in one region. Price: $0.01 USDC per call, paid with x402 on Base.

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": {
      "vcpu": "<vcpu>",
      "memory": "<memory>"
    },
    "name": "cloudprice_compute"
  }
}

Input Schema

Name	Required	Description
`type`	No	on-demand \| spot \| any
`vcpu`	Yes	vcpu
`limit`	No	limit
`memory`	Yes	GiB
`region`	No	e.g. eu-west-3

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

No annotations are provided, but the description proactively discloses the most consequential behavioral trait: it is a paid call ($0.01 USDC per call, paid via x402 on Base). That is real context an agent cannot get from the schema and could otherwise trigger unknowingly. It omits return shape, result count behavior, and any rate/limit semantics.

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 sentences, zero filler. The functional contract comes first and the pricing/payment caveat second, which is the right ordering for a paid tool.

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?

Covers purpose, filter semantics, cost, and payment mechanism for a 5-parameter read query with no output schema. The remaining gap is what comes back — a single cheapest instance or a ranked list — and what 'limit' controls, which an agent would want before paying per call.

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%, but the schema descriptions are near-empty ("vcpu", "limit", "GiB"). The description usefully adds the threshold semantics ("at least the given vCPU and memory") — a minimum, not an exact match — and restates the type values (on-demand/spot), but leaves 'limit' completely undefined in both schema and description.

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?

States a specific verb+resource and the exact selection semantics: cheapest AWS EC2 Linux instances meeting minimum vCPU/memory, on-demand or spot, optionally one region. An agent immediately knows what it will get. It never names the sibling it is not (cloudprice_instance, cloudprice_gpu), so differentiation is inferred from the name rather than stated.

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 query shape ("cheapest ... with at least the given vCPU and memory"), which tells an agent this is a spec-constrained price lookup. There is no explicit when-to-use, no when-not-to-use, and no routing to cloudprice_instance or cloudprice_gpu, so an agent comparing siblings must guess.

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

All Genexxis paid agent tools (x402) tools Inspect

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

Need Help?