Skip to main content
Glama
FTHTrading

Genesis402

by FTHTrading
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Call any endpoint

genesis402_call

Call 360+ endpoints for DeFi, SEC, web, domain, AI, and multi-chain data. Unpaid calls return a quote; paid calls return results.

Instructions

Calls any of the 360 Genesis402 endpoints by name (DeFi, SEC filings, research, web/domain intel, AI text tools, multi-chain reads). Prices $0.001-$0.25 USDC on Base. Use for any endpoint without a dedicated tool; look up the name and parameters with genesis402_catalog first. Parameters are validated for free before any quote. Without payment_signature (or a local payer) it returns the exact price quote and signs nothing; with payment it returns the result plus the settlement details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNoParameters for that endpoint as an object, matching the parameter schema shown in genesis402_catalog. Omit if the endpoint takes none.
endpointYesEndpoint name exactly as listed by genesis402_catalog, e.g. "defi-yields" or "wallet-brief" (a leading slash is ignored).
payment_signatureNoOptional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.2
    • addedInput schema / properties / endpoint / description
      Added value: +"Endpoint name exactly as listed by genesis402_catalog, e.g. \"defi-yields\" or \"wallet-brief\" (a leading slash is ignored)."
    • addedInput schema / properties / params / description
      Added value: +"Parameters for that endpoint as an object, matching the parameter schema shown in genesis402_catalog. Omit if the endpoint takes none."
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first."New value: +"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it."
  2. First observedv0.3.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations (readOnlyHint=false, openWorldHint=true) are present; the description complements them by explaining the two modes (quote-only vs. execution), the free validation of parameters before quoting, and the absence of signing without payment_signature. It adds critical behavioral context beyond what annotations provide and does not contradict them.

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 tightly packed with functional detail in four sentences, front-loading the purpose and usage. Every sentence adds value (purpose, scope, prerequisite, payment behavior) without redundancy or fluff.

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?

For a generic dispatcher covering 360 endpoints, the description is complete: it explains how to start (catalog), how to invoke (endpoint name + params), and the payment flow both with and without signature. It does not need to detail every endpoint's response format since that is catalog-driven, and no output schema is provided.

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?

Schema coverage is 100%, so the description's role is to add usage nuance. It clarifies that 'params' must match the catalog schema, that 'endpoint' should be exactly as listed, and that parameters are validated for free before any quote. This adds meaning beyond the raw schema definitions, though not exhaustively.

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 states a clear verb ('calls'), a specific resource ('any of the 360 Genesis402 endpoints'), and enumerates categories (DeFi, SEC filings, etc.), which distinguishes it from dedicated sibling tools. It explicitly frames the tool as a generic dispatcher for endpoints lacking a dedicated tool.

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?

Provides explicit when-to-use ('Use for any endpoint without a dedicated tool') and a required prerequisite action ('look up the name and parameters with genesis402_catalog first'). It also differentiates the payment flow (quote vs. transaction) and clarifies that no charge occurs without a payment signature.

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

Deploy Server

Other Tools