Skip to main content
Glama

aeX402 — Cross-Chain DeFi MCP: LINQ, AMM, Bridge, AI

by com.aex402
OverviewDiscussionsAdmin

discover_programs

Discover on-chain programs/contracts across every chain this RPC supports (Solana, Slonana SVM, Robinhood, HyperEVM, Ethereum, Base, Stable, Plasma, Tempo, Codex). Returns a curated seed MERGED with programs/contracts AUTO-DISCOVERED from recent block activity (refreshed hourly) — each carries an activity count of recent invocations/calls; entries with type "discovered" were seen live on-chain but not yet named. Use this to learn what is actually active on-chain right now, then describe_program to introspect any specific address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoFilter to one chain: solana | slonana | robinhood | hyperevm | ethereum | base | stable | plasma | tempo | codex. Omit or "all" for every chain.all

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNocaveats about what this scan did and did not see
chainNo
countNo
tokensNotoken contracts seen alongside programs
coverageNowhat this scan enumerated: a string on the single-chain response, the full per-chain map on the all-chains response
programsNoarray on the single-chain response; a per-chain {chain: program[]} map on the all-chains response
discoveredNoauto-discovered (not curated) entries

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / coverage / description
      Previous value: -"what this scan did and did not enumerate"New value: +"what this scan enumerated: a string on the single-chain response, the full per-chain map on the all-chains response"
    • changedOutput schema / properties / coverage / type
      Previous value: -"string"New value: +[
+  "string",
+  "object"
+]
    • addedOutput schema / properties / programs / description
      Added value: +"array on the single-chain response; a per-chain {chain: program[]} map on the all-chains response"
    • changedOutput schema / properties / programs / type
      Previous value: -"array"New value: +[
+  "array",
+  "object"
+]
  2. Changed6 schema fields changed
    • addedOutput schema / properties / coverage
      Added value: +{
+  "description": "what this scan did and did not enumerate",
+  "type": "string"
+}
    • addedOutput schema / properties / note
      Added value: +{
+  "description": "caveats about what this scan did and did not see",
+  "type": "string"
+}
    • removedOutput schema / properties / programs / items / description
      Removed value: -"id, name, type, note, activity"
    • addedOutput schema / properties / programs / items / properties
      Added value: +{
+  "activity": {
+    "description": "recent invocations/calls",
+    "type": "integer"
+  },
+  "id": {
+    "description": "program/contract address",
+    "type": "string"
+  },
+  "name": {
+    "type": "string"
+  },
+  "note": {
+    "type": "string"
+  },
+  "type": {
+    "description": "'core' | 'curated' | 'discovered'",
+    "type": "string"
+  }
+}
    • addedOutput schema / properties / programs / items / required
      Added value: +[
+  "id"
+]
    • addedOutput schema / properties / tokens
      Added value: +{
+  "description": "token contracts seen alongside programs",
+  "type": "integer"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / chain / description
      Previous value: -"Filter to one chain: solana | slonana | robinhood | hyperevm. Omit or \"all\" for every chain."New value: +"Filter to one chain: solana | slonana | robinhood | hyperevm | ethereum | base | stable | plasma | tempo | codex. Omit or \"all\" for every chain."
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the data composition (curated seed + auto-discovered), refresh cadence (hourly), the activity field semantics, and what type='discovered' means. It could be more explicit about read-only guarantees or pagination, but it is transparent about core behavior.

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 front-loaded with the primary purpose, followed by a dense but relevant explanation of the returned data, and ends with a practical usage pointer. No filler or redundancy.

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 one-parameter, discovery-only tool with an output schema, the description covers the data source freshness, the discovered-vs-seed distinction, activity counts, and the intended next step. This is enough for an agent to call it 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 coverage is 100% and the single chain parameter is already fully described with allowed values and default. The tool description repeats the chain list but adds no meaning beyond the schema, so the baseline of 3 applies.

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 clearly states the tool's function: discovering on-chain programs/contracts across supported chains. It distinguishes itself by explaining the curated seed merged with hourly auto-discovered programs ritually and by directing follow-up introspection to describe_program.

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?

It explicitly tells the agent to use this tool 'to learn what is actually active on-chain right now' and then chain describe_program for a specific address. This provides a clear use case and a sibling alternative, though it doesn't spell out negative cases or other exclusions.

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

All aeX402 — Cross-Chain DeFi MCP: LINQ, AMM, Bridge, AI 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