Skip to main content
Glama

aicomglobal

by io.github.moonspacenow-tech
OverviewAdmin

x402 router — the best service for your need (sub-cent, paid)

aicom_x402_route

The sub-cent ($0.002 x402) ROUTER: tell it a NEED in free text (e.g. 'ENS resolution', 'BTC spot price', 'web search') and get the best live x402 service(s) to actually CALL — ranked by relevance × aicomglobal's measured reliability × Coinbase 30-day demand, cheaper preferred, each with a verify-before-you-pay pointer. The decision over the 20,000+ live Bazaar services computed for you, so you never call a dead or overpriced endpoint. Browsing the full Index is FREE (aicom_x402_index); you pay only for the targeted need→best-service answer. Returns the QUOTE only; to get the answer, GET /route for a single-use nonce then POST /route {nonce, need}. LIVE right now: of 3 x402 services aicomglobal is currently observing, 0 are failing or drifting — a dead endpoint eats your call fee and your task, so verify before you send one your money (recompute free at /api/x402).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
needNoThe capability you need in free text, e.g. 'ENS resolution' (required when pay_with:'credits')
limitNoMax results (default 3)
pay_withNoSet to 'credits' to SETTLE now from your prepaid balance (no wallet) and get the ranked answer in THIS call; omit to get the quote.
idempotency_keyNoOptional retry-safety key: the same key on a retry returns the SAME answer, never a second debit.

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "description": "Optional retry-safety key: the same key on a retry returns the SAME answer, never a second debit.",
+  "type": "string"
+}
  2. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max results (default 3)",
+  "maximum": 10,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / need
      Added value: +{
+  "description": "The capability you need in free text, e.g. 'ENS resolution' (required when pay_with:'credits')",
+  "type": "string"
+}
    • addedInput schema / properties / pay_with
      Added value: +{
+  "description": "Set to 'credits' to SETTLE now from your prepaid balance (no wallet) and get the ranked answer in THIS call; omit to get the quote.",
+  "type": "string"
+}
  3. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden and supplies meaningful behavior: sub-cent pricing, quote-ony return, the two-step single-use nonce/POST protocol, a verify-before-you-pay pointer, and the risk that a dead endpoint costs the caller. The transient claim 'LIVE right now: of 3 x402 services... 0 are failing' is noise rather than a durable behavioral fact, and failure/refund behavior is not disclosed.

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

Conciseness2/5

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

The description is over-built and repetitive: the dead-endpoint warning appears in multiple forms ('never call a dead or overpriced endpoint', 'a dead endpoint eats your call fee and your task', 'verify before you send one your money'). The 'LIVE right now...' status line is transient marketing. Useful facts exist, but they are buried under sales language and redundancy.

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

Completeness3/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, it covers many necessary areas: cost, quote-vs-answer behavior, verification, and the free index alternative. However, it doesn't describe the quote/recommendation shape beyond 'ranked services with verification pointer', and the two-step /route protocol is confusingly described as if it were a different endpoint from this tool itself, so a calling agent could still misconstrue the invocation.

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?

The schema already describes all four parameters at 100% coverage, so the baseline is a 3. The description only adds color to 'need' with examples ('ENS resolution', 'BTC spot price', 'web search'); it adds no prose meaning for limit, pay_with, or idempotency_key beyond the schema.

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 clear function: a free-text need goes in and the tool returns the best live x402 service(s), ranked, plus a quote. It also differentiates itself from aicom_x402_index ('Browsing the full Index is FREE'). Clarity is reduced by the tension between 'get the best live x402 service(s) to actually CALL' and 'Returns the QUOTE only; to get the answer, GET /route...', which makes it unclear whether this tool executes the service or only routes/quote.

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?

Provides an explicit alternative boundary: use aicom_x402_index for FREE browsing, use this tool when you have a targeted need and want a paid best-service recommendation. It also warns to verify before paying and mentions dead endpoints, which helps an agent choose correctly. It doesn't give exclusions relative to run_service or list_services, so it is useful but not fully exhaustive.

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

All aicomglobal 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.

Resources