Skip to main content
Glama

aicomglobal

by io.github.moonspacenow-tech
OverviewAdmin

Your prepaid credit balance (the wallet-free way to pay)

aicom_credits

FREE. Check your aicomglobal credit balance and how to fund + spend it. Credit is a closed-loop prepaid balance for paying IN-BAND (over /a2a or /mcp, where x402 can't ride the transport): settle the per-call actions (aicom_verdict / aicom_x402_route / aicom_attest) from the balance by passing pay_with:'credits' — the signed artifact returns IN the tool call, no wallet, no chain, no 402. FUND IT AUTONOMOUSLY: GET /credits/x402/starter for a nonce, then POST {nonce} and settle $5 USDC over x402 yourself — no human, no card. (Or your principal may fund by card at its discretion: POST /credits/checkout {pack}.) Credit is prepaid, closed-loop, non-transferable and non-refundable — spendable only on aicomglobal's own actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

No annotations provided, so description fully carries burden. It details credit nature (closed-loop, non-transferable, non-refundable), spending mechanism (pay_with:'credits'), and funding flows (x402 or card). No contradictions.

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

Conciseness4/5

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

Description is well-structured and informative, but slightly long. Each sentence adds value, but could be more concise while retaining clarity.

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?

With no parameters and no output schema, the description covers all necessary context: what credit is, how to check balance, fund, and spend. Complete for agent decision-making.

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

Parameters4/5

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

No parameters in schema; baseline is 4. Description doesn't need to add parameter info, and it doesn't, which 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?

Description clearly states verb+resource: check credit balance and how to fund+spend. It distinguishes from siblings by being the only tool about prepaid credits, with no overlap.

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?

Explicitly says when to use credits (for in-band payment where x402 can't ride) and provides funding instructions. Could explicitly state when not to use, but context is clear.

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