Skip to main content
Glama

SQD

by io.github.subsquid-labs
OverviewDiscussionsAdmin

Find a token or contract

portal_resolve_entity
Read-only

Resolve user-facing blockchain entities into query-ready identifiers, with ambiguity kept explicit.

COMMON USER ASKS:

  • Resolve USDC on Base

  • Resolve WETH on Ethereum

  • Resolve BAYC contract

FIRST CHOICE FOR:

  • resolving a token symbol like USDC to token contract addresses

  • resolving EVM contract aliases, protocol names, pool identifiers, or Hyperliquid coin names before querying

  • checking which token-list addresses a symbol maps to before querying logs or transfers

  • turning a user-friendly token name into deterministic EVM filters

WHEN TO USE:

  • The user names a token symbol such as USDC, WETH, DAI, or PEPE and you need contract addresses before querying raw data.

  • The user names a well-known EVM contract, protocol, pool identifier, or Hyperliquid ticker and you need a deterministic follow-up filter.

  • You need to disambiguate bridged token variants on an EVM network.

  • You want a source-backed token address rather than relying on memory or hardcoded constants.

DON'T USE:

  • You already have the exact address, pool id, protocol slug, or coin filter and can pass it directly.

EXAMPLES:

  • Resolve USDC on Base: {"network":"base-mainnet","kind":"token","query":"USDC","limit":10}

  • Resolve WETH on Ethereum: {"network":"ethereum-mainnet","kind":"token","query":"WETH","limit":5}

  • Resolve BAYC contract: {"network":"ethereum-mainnet","kind":"contract","query":"bored apes"}

  • Resolve Hyperliquid coin: {"kind":"hyperliquid_coin","query":"bitcoin"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoEntity kind to resolve: token, contract alias/address, pool identifier, protocol name, or Hyperliquid coin/ticker.token
limitNoMaximum matches to return.
queryYesEntity string to resolve, e.g. "USDC", "bayc", "uniswap", "BTC", or "0x...".
networkNoNetwork name or alias when the entity is network-scoped, e.g. "base", "ethereum", "arbitrum-one", or "hyperliquid-fills".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_uiNoChart, table, and follow-up presentation metadata.
_appNoSQD Explorer identity and host-render state.
_llmNoHints to locate the primary evidence.
_metaNoNetwork, block range, timing, and row counts.
errorNoStructured failure details.
itemsNoPrimary rows for list results.
valueNoPrimary scalar result.
answerNoAnswer grounded in the returned data.
_noticeNoLimitation or truncation notice.
_serverNoSQD server name, exact version, and git commit.
displayNoLabels for presenting the result.
_noticesNoLimitation or truncation notices.
_summaryNoHuman-readable summary.
_coverageNoWindow and result completeness.
_evidenceNoReplayable arguments, digest, row count, and receipt.
_orderingNoOrdering guarantees.
_executionNoBounded execution and scan details.
_freshnessNoFreshness and finality.
next_stepsNoSafe follow-up actions and continuation guidance.
_paginationNoPagination state and next_cursor.
investigationNoEvidence paths, pivots, and limitations.
pipes_handoffNoSQD Pipes guidance for custom data needs.
_tool_contractNoTool identity, intent, and chain families.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed51 schema fields changed
    • removedOutput schema / properties / _app / additionalProperties
      Removed value: -{}
    • changedOutput schema / properties / _app / description
      Previous value: -"SQD Explorer identity and honest host-render state."New value: +"SQD Explorer identity and host-render state."
    • removedOutput schema / properties / _app / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / _app / type
      Removed value: -"object"
    • changedOutput schema / properties / _coverage / description
      Previous value: -"Completeness of the requested window and result set."New value: +"Window and result completeness."
    • removedOutput schema / properties / _evidence / additionalProperties
      Removed value: -{}
    • changedOutput schema / properties / _evidence / description
      Previous value: -"Replayable arguments, exact-data digest, row count, and completeness receipt."New value: +"Replayable arguments, digest, row count, and receipt."
    • removedOutput schema / properties / _evidence / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / _evidence / type
      Removed value: -"object"
    • removedOutput schema / properties / _execution / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / _execution / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / _execution / type
      Removed value: -"object"
    • changedOutput schema / properties / _freshness / description
      Previous value: -"Freshness and finality information for the returned data."New value: +"Freshness and finality."
    • changedOutput schema / properties / _llm / description
      Previous value: -"Hints that help an AI client locate the primary evidence."New value: +"Hints to locate the primary evidence."
    • removedOutput schema / properties / _meta / additionalProperties
      Removed value: -{}
    • changedOutput schema / properties / _meta / description
      Previous value: -"Network, block range, timing, and row-count metadata."New value: +"Network, block range, timing, and row counts."
    • removedOutput schema / properties / _meta / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / _meta / type
      Removed value: -"object"
    • changedOutput schema / properties / _notice / description
      Previous value: -"Important limitation or truncation notice."New value: +"Limitation or truncation notice."
    • changedOutput schema / properties / _notices / description
      Previous value: -"Important limitations or truncation notices."New value: +"Limitation or truncation notices."
    • changedOutput schema / properties / _ordering / description
      Previous value: -"Ordering guarantees for the returned data."New value: +"Ordering guarantees."
    • removedOutput schema / properties / _pagination / additionalProperties
      Removed value: -{}
    • changedOutput schema / properties / _pagination / description
      Previous value: -"Pagination state and an optional continuation cursor."New value: +"Pagination state and next_cursor."
    • removedOutput schema / properties / _pagination / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / _pagination / type
      Removed value: -"object"
    • changedOutput schema / properties / _server / description
      Previous value: -"Observable SQD server identity and exact release version."New value: +"SQD server name, exact version, and git commit."
    • addedOutput schema / properties / _server / properties / commit
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / _server / required
      Previous value: -[
-  "name",
-  "version"
-]New value: +[
+  "name",
+  "version",
+  "commit"
+]
    • changedOutput schema / properties / _summary / description
      Previous value: -"Human-readable summary of the result."New value: +"Human-readable summary."
    • removedOutput schema / properties / _tool_contract / additionalProperties
      Removed value: -{}
    • changedOutput schema / properties / _tool_contract / description
      Previous value: -"Tool identity, intent, and supported blockchain families."New value: +"Tool identity, intent, and chain families."
    • removedOutput schema / properties / _tool_contract / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / _tool_contract / type
      Removed value: -"object"
    • changedOutput schema / properties / _ui / description
      Previous value: -"Optional chart, table, and follow-up presentation metadata."New value: +"Chart, table, and follow-up presentation metadata."
    • changedOutput schema / properties / answer / description
      Previous value: -"Concise answer grounded in the returned blockchain data."New value: +"Answer grounded in the returned data."
    • removedOutput schema / properties / display / additionalProperties
      Removed value: -{}
    • changedOutput schema / properties / display / description
      Previous value: -"Plain-language labels for presenting the result."New value: +"Labels for presenting the result."
    • removedOutput schema / properties / display / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / display / type
      Removed value: -"object"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured failure details when the tool cannot complete the request."New value: +"Structured failure details."
    • removedOutput schema / properties / investigation / additionalProperties
      Removed value: -{}
    • changedOutput schema / properties / investigation / description
      Previous value: -"Evidence paths, useful pivots, and result limitations."New value: +"Evidence paths, pivots, and limitations."
    • removedOutput schema / properties / investigation / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / investigation / type
      Removed value: -"object"
    • changedOutput schema / properties / items / description
      Previous value: -"Primary result rows when the tool returns a list."New value: +"Primary rows for list results."
    • removedOutput schema / properties / next_steps / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / next_steps / properties
      Removed value: -{
-  "actions": {
-    "items": {
-      "additionalProperties": {},
-      "propertyNames": {
-        "type": "string"
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "continuation": {
-    "additionalProperties": {},
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  "custom_data": {
-    "additionalProperties": {},
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  }
-}
    • removedOutput schema / properties / next_steps / required
      Removed value: -[
-  "actions"
-]
    • removedOutput schema / properties / next_steps / type
      Removed value: -"object"
    • changedOutput schema / properties / pipes_handoff / description
      Previous value: -"Optional SQD Pipes guidance for custom data needs."New value: +"SQD Pipes guidance for custom data needs."
    • changedOutput schema / properties / value / description
      Previous value: -"Primary result when the tool returns a scalar value."New value: +"Primary scalar result."
  2. Changed2 schema fields changed
    • changedOutput schema / properties / _app / description
      Previous value: -"SQD Blockchain Activity Explorer identity and honest host-render state."New value: +"SQD Explorer identity and honest host-render state."
    • addedOutput schema / properties / _server
      Added value: +{
+  "additionalProperties": false,
+  "description": "Observable SQD server identity and exact release version.",
+  "properties": {
+    "name": {
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "version"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedOutput schema / properties / _app
      Added value: +{
+  "additionalProperties": {},
+  "description": "SQD Blockchain Activity Explorer identity and honest host-render state.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedOutput schema / properties / _evidence
      Added value: +{
+  "additionalProperties": {},
+  "description": "Replayable arguments, exact-data digest, row count, and completeness receipt.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "_coverage": {
+      "description": "Completeness of the requested window and result set."
+    },
+    "_execution": {
+      "additionalProperties": {},
+      "description": "Bounded execution and scan details.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_freshness": {
+      "description": "Freshness and finality information for the returned data."
+    },
+    "_llm": {
+      "description": "Hints that help an AI client locate the primary evidence."
+    },
+    "_meta": {
+      "additionalProperties": {},
+      "description": "Network, block range, timing, and row-count metadata.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_notice": {
+      "description": "Important limitation or truncation notice.",
+      "type": "string"
+    },
+    "_notices": {
+      "description": "Important limitations or truncation notices.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "_ordering": {
+      "description": "Ordering guarantees for the returned data."
+    },
+    "_pagination": {
+      "additionalProperties": {},
+      "description": "Pagination state and an optional continuation cursor.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_summary": {
+      "description": "Human-readable summary of the result.",
+      "type": "string"
+    },
+    "_tool_contract": {
+      "additionalProperties": {},
+      "description": "Tool identity, intent, and supported blockchain families.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_ui": {
+      "description": "Optional chart, table, and follow-up presentation metadata."
+    },
+    "answer": {
+      "description": "Concise answer grounded in the returned blockchain data.",
+      "type": "string"
+    },
+    "display": {
+      "additionalProperties": {},
+      "description": "Plain-language labels for presenting the result.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "error": {
+      "additionalProperties": {},
+      "description": "Structured failure details when the tool cannot complete the request.",
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "origin": {
+          "type": "string"
+        },
+        "retry_after_ms": {
+          "type": "number"
+        },
+        "retryable": {
+          "type": "boolean"
+        },
+        "suggestions": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "summary": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "origin",
+        "summary",
+        "retryable",
+        "suggestions"
+      ],
+      "type": "object"
+    },
+    "investigation": {
+      "additionalProperties": {},
+      "description": "Evidence paths, useful pivots, and result limitations.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "items": {
+      "description": "Primary result rows when the tool returns a list.",
+      "items": {},
+      "type": "array"
+    },
+    "next_steps": {
+      "additionalProperties": {},
+      "description": "Safe follow-up actions and continuation guidance.",
+      "properties": {
+        "actions": {
+          "items": {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "continuation": {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "custom_data": {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        }
+      },
+      "required": [
+        "actions"
+      ],
+      "type": "object"
+    },
+    "pipes_handoff": {
+      "description": "Optional SQD Pipes guidance for custom data needs."
+    },
+    "value": {
+      "description": "Primary result when the tool returns a scalar value."
+    }
+  },
+  "type": "object"
+}
  6. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  7. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is known. The description adds useful behavioral context: ambiguity is kept explicit, it maps symbols to token-list addresses, and it returns source-backed addresses rather than relying on memory. This goes beyond the structured annotations without contradicting 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 well-structured with clear headers: COMMON USER ASKS, FIRST CHOICE FOR, WHEN TO USE, DON'T USE, and EXAMPLES. It is longer than average but every section earns its place by providing actionable routing information. The core purpose is front-loaded in the first sentence.

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?

The description covers all entity kinds, network scoping, common user intents, exclusions, and provides examples. An output schema exists to handle return-value details, so nothing critical is missing. For a resolver tool with this complexity, the description is complete.

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 description coverage is 100%, so the baseline is 3. The description adds value with concrete worked examples for each kind (e.g., resolving USDC, WETH, BAYC, Hyperliquid bitcoin), clarifying how network, kind, query, and limit interact. This makes parameter usage more concrete than the schema alone.

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 opens with a clear, specific statement: 'Resolve user-facing blockchain entities into query-ready identifiers, with ambiguity kept explicit.' It names the resource (blockchain entities) and the verb (resolve), and the title reinforces the function. This clearly differentiates portal_resolve_entity from the many query-focused sibling tools.

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?

The description contains explicit 'FIRST CHOICE FOR', 'WHEN TO USE', and 'DON'T USE' sections. It lists concrete scenarios (resolving USDC, WETH, BAYC, Hyperliquid coins) and tells the agent exactly when not to call this tool, such as when an exact address or filter is already known. This is exemplary usage guidance.

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

All SQD 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