Skip to main content
Glama

Emberlane Crypto Intelligence & Agent APIs

List Emberlane x402 API Endpoints

emberlane_list_endpoints
Read-onlyIdempotent

List all 18 Emberlane x402 v2 pay-per-call API endpoints (Shield security, Alpha funding-rate arb & crypto signals, Polymarket edges & CLOB orderbook slippage, DeFi stablecoin yields, 6-chain gas oracle, company enrichment, SEC EDGAR filings, domain recon, PDF text extraction, and Render headless Chromium) with live Base/Polygon/Arbitrum USDC pricing and schemas.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "emberlane_list_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that results carry live Base/Polygon/Arbitrum USDC pricing and schemas, which is useful return-content context, but with no output schema it stops short of describing the actual response shape (per-endpoint fields, array vs wrapper object).

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?

The verb, count and scope are front-loaded in the first clause, which is the right structure for a discovery tool. The trailing parenthetical enumerating twelve product categories is dense but earns its place as a relevance signal for an agent deciding whether this catalog covers its need.

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?

For a zero-parameter, read-only catalog call with no output schema, the description covers what the tool is, that the list is complete (18), and what the entries contain (pricing, schemas). What remains thin is the response structure and whether any auth/credential is needed to retrieve pricing, but neither is critical to selecting the tool.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. It correctly implies the call is unfiltered — the full catalog of 18 is returned regardless of any selection.

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 and resource ("List all 18 Emberlane x402 v2 pay-per-call API endpoints") and enumerates the covered domains, so an agent knows exactly what it returns. It does not, however, distinguish itself from the sibling *_preview tools or say that this is the discovery step preceding them.

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 only implied: an agent can infer this is the catalog/discovery call for the Emberlane family, and "all 18" signals a fixed, non-paginated listing. There is no explicit when-to-use, when-not-to-use, or pointer to the alpha/market-pulse/scan-token preview tools as the follow-up actions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources