CryptoPulse Data API

ens

[$0.001 USDC per call via x402] ENS lookup: resolve a .eth name to an address (or an address to its primary name) with avatar and profile records (url, twitter, github, email, description).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	ENS name such as vitalik.eth, or a 0x address for reverse lookup

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the cost model ('$0.001 USDC per call via x402'), which is critical for a paid endpoint, and enumerates what comes back (avatar, url, twitter, github, email, description). It does not say what happens when a name fails to resolve or when records are absent, which keeps it from a 5.

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?

A single dense sentence with no waste. The price tag is placed first, which slightly delays the purpose statement, but the rest is tightly packed and front-loaded with the key capability.

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 one-parameter lookup with no output schema and no annotations, the description supplies the essential missing pieces: cost, resolution direction, and returned record fields. Only edge-case behavior (unresolved names, partial records) is left unspecified.

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% for the single 'name' parameter, and the schema description already explains that it accepts an ENS name or a 0x address for reverse lookup. The description restates the same duality but adds no syntax, validation, or formatting detail beyond the schema, so the baseline 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 states a specific verb and resource ('ENS lookup: resolve a .eth name to an address') and covers the reverse direction plus the record types returned. The opaque tool name 'ens' is fully compensated for, and the function is unmistakably distinct from siblings like wallet or token_score.

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 makes clear the two usage modes: forward resolution from a .eth name and reverse lookup from a 0x address to a primary name. It does not name alternatives or exclusions, but no sibling tool overlaps this capability, so context is sufficient.

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

All CryptoPulse Data API tools Inspect

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

Need Help?