Skip to main content
Glama

Name Whisper — ENS Intelligence Layer

by ai.namewhisper
OverviewDiscussionsAdmin

get_wallet_portfolio

Read-only

Get all ENS names owned by a wallet address. Returns each name with label, tags, expiry, lifecycle status, registration date, and active listing/offer prices. Useful for portfolio analysis and wallet profiling. THE tool for any question about the connected wallet's OWN names by lifecycle window ("my names close to premium" → status:"GRACE_PERIOD"; "my names about to expire" → "EXPIRING_SOON"; "which of mine are in premium" → "PREMIUM_AUCTION"). get_expiring_names is market-wide and cannot answer those. summary counts the WHOLE portfolio; names is one page of totalMatching — page with offset when returned < totalMatching.

If you are authenticated via ERC-8128 and omit the wallet parameter, your own wallet is used automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 100, max 200)
offsetNoPagination offset. Page until `totalMatching` names have been seen — the summary counts the whole portfolio, the rows are one page.
statusNoLifecycle filter, applied BEFORE paging. "GRACE_PERIOD" = expired ≤90 days, the window right before premium — use it for "my names close to / about to hit premium". "EXPIRING_SOON" = active, ≤90 days left — "about to expire / about to go to grace". "PREMIUM_AUCTION" = past grace, in the 21-day Dutch auction (registerable by anyone, incl. this wallet; on-chain-confirmed). "ACTIVE" = >90 days left. Default "all".all
walletYesEthereum wallet address (0x...) or ENS name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / offset / description
      Previous value: -"Pagination offset"New value: +"Pagination offset. Page until `totalMatching` names have been seen — the summary counts the whole portfolio, the rows are one page."
    • addedInput schema / properties / status
      Added value: +{
+  "default": "all",
+  "description": "Lifecycle filter, applied BEFORE paging. \"GRACE_PERIOD\" = expired ≤90 days, the window right before premium — use it for \"my names close to / about to hit premium\". \"EXPIRING_SOON\" = active, ≤90 days left — \"about to expire / about to go to grace\". \"PREMIUM_AUCTION\" = past grace, in the 21-day Dutch auction (registerable by anyone, incl. this wallet; on-chain-confirmed). \"ACTIVE\" = >90 days left. Default \"all\".",
+  "enum": [
+    "ACTIVE",
+    "EXPIRING_SOON",
+    "GRACE_PERIOD",
+    "PREMIUM_AUCTION",
+    "all"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true. The description adds important behavioral context: pagination semantics ('summary counts the WHOLE portfolio; names is one page of totalMatching'), filtering before paging, and auth behavior via ERC-8128. No contradiction with annotations.

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 description is longer than average but well-structured: purpose, return fields, sibling differentiation, pagination, auth. It is front-loaded and each block earns its place, though status examples partly repeat the schema descriptions.

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 compensates by listing key returned fields and explaining pagination. It covers auth, lifecycle windows, sibling alternatives, and parameter behavior thoroughly enough for an agent to invoke the tool correctly.

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?

Input schema already covers all four parameters at 100% with detailed descriptions, giving a baseline of 3. The description adds value by giving lifecycle-status usage examples and clarifying portfolio vs. page semantics, though some content overlaps with the schema.

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?

States a specific verb and resource: 'Get all ENS names owned by a wallet address.' It also enumerates returned fields and explicitly differentiates itself from the sibling get_expiring_names, making selection unambiguous.

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 guidance with concrete lifecycle examples ('my names close to premium', 'my names about to expire'), and names the alternative tool it is not. It also explains the authentication behavior where omitting wallet uses the connected wallet.

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

All Name Whisper — ENS Intelligence Layer 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