Skip to main content
Glama
Sign In

Agent Kiosk — 23-in-1 B2A Intelligence, Action & x402 API

by io.github.ralf9090
OverviewDiscussionsAdmin

token_due_diligence

Read-onlyIdempotent

Institutional 3-in-1 Token Due Diligence Report ($0.10 USDC). Combines GoPlus on-chain honeypot/tax security audit, DexScreener DEX order-flow alpha & liquidity depth, and live Reddit/HN social sentiment into a composite investment grade (A-F).

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain network (default: 'base')
queryYesToken symbol (e.g., 'AERO', 'VIRTUAL', 'PEPE') or 0x contract address
x_api_keyNoOptional ak_live_... 30-day Prepaid API Pass key to unlock the full unmasked dataset
payment_signatureNoOptional x402 v2/v1 Base64 or JSON EIP-3009 USDC payment signature to unlock the full unmasked dataset directly via MCP

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / payment_signature
      Added value: +{
+  "description": "Optional x402 v2/v1 Base64 or JSON EIP-3009 USDC payment signature to unlock the full unmasked dataset directly via MCP",
+  "type": "string"
+}
    • addedInput schema / properties / x_api_key
      Added value: +{
+  "description": "Optional ak_live_... 30-day Prepaid API Pass key to unlock the full unmasked dataset",
+  "type": "string"
+}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds meaningful non-structural context: a $0.10 USDC cost and the composite A-F output, both of which shape invocation decisions. It does not itself explain the masked-vs-unmasked dataset behavior, but that is carried in the schema.

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?

Two dense sentences with the value proposition (the composite deliverable and its sources) front-loaded. Little waste, though the parenthetical pricing/grade details slightly compress into the same block.

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 output schema, the description adequately conveys the return shape (a composite A-F investment grade synthesized from three named sources) plus cost. For a 4-param tool with full schema coverage, this is complete enough to call correctly.

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 description coverage is 100%, so the schema already documents query, chain, x_api_key, and payment_signature. The description adds no parameter-level syntax or format detail (e.g., chain defaults, symbol vs address handling). Baseline 3 is correct when the schema does the heavy lifting.

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 deliverable ('Institutional 3-in-1 Token Due Diligence Report') and enumerates its three components: GoPlus security audit, DexScreener order-flow/liquidity, and Reddit/HN sentiment producing an A-F grade. This is clear and specific. However, it does not differentiate from overlapping siblings like security_audit (on-chain audit) or token_alpha (DEX/alpha), so an agent must infer the distinction.

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 deliverable (reach for this when you want a composite due-diligence grade on a token), but no explicit when-to-use, when-not-to-use, or named alternatives are given. It also fails to route the agent between this and the overlapping security_audit/token_alpha siblings.

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

All Agent Kiosk — 23-in-1 B2A Intelligence, Action & x402 API toolsInspect
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