blockscout-mcp-server

Lookup Token by Symbol

lookup_token_by_symbol

Read-only

Search for token addresses by symbol or name. Returns multiple potential matches based on symbol or token name similarity. Only the first 7 matches from the Blockscout API are returned.

Input Schema

TableJSON Schema

Name	Required	Description
`symbol`	Yes	Token symbol or name to search for
`chain_id`	Yes	The ID of the blockchain
`session_id`	No	Opaque session identifier.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	The main data payload of the tool's response.
`notes`	No	A list of important contextual notes, such as warnings about data truncation or data quality issues.
`pagination`	No	Pagination information, present only if the 'data' is a single page of a larger result set.
`content_text`	No	Optional human-readable summary used for MCP content responses.
`instructions`	No	A list of suggested follow-up actions or instructions for the LLM to plan its next steps.
`data_description`	No	A list of notes explaining the structure, fields, or conventions of the 'data' payload.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

addedInput schema / properties / session_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Opaque session identifier.",
+  "title": "Session Id"
+}

Changed7 schema fields changedMay 1, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / chain_id / title
```
Added value: +"Chain Id"
```

changedInput schema / properties / symbol / description

Previous value: -"Token symbol or name to search"New value: +"Token symbol or name to search for"

addedInput schema / properties / symbol / title
```
Added value: +"Symbol"
```

addedInput schema / title

Added value: +"lookup_token_by_symbolArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "NextCallInfo": {
+      "description": "A structured representation of the tool call required to get the next page.",
+      "properties": {
+        "params": {
+          "additionalProperties": true,
+          "description": "A complete dictionary of parameters for the next tool call, including the new cursor.",
+          "title": "Params",
+          "type": "object"
+        },
+        "tool_name": {
+          "description": "The name of the tool to call for the next page.",
+          "title": "Tool Name",
+          "type": "string"
+        }
+      },
+      "required": [
+        "tool_name",
+        "params"
+      ],
+      "title": "NextCallInfo",
+      "type": "object"
+    },
+    "PaginationInfo": {
+      "description": "Contains the structured information needed to retrieve the next page of results.",
+      "properties": {
+        "next_call": {
+          "$ref": "#/$defs/NextCallInfo",
+          "description": "The structured tool call required to fetch the subsequent page."
+        }
+      },
+      "required": [
+        "next_call"
+      ],
+      "title": "PaginationInfo",
+      "type": "object"
+    },
+    "TokenSearchResult": {
+      "description": "Represents a single token found by a search query.",
+      "properties": {
+        "address": {
+          "description": "The contract address of the token.",
+          "title": "Address",
+          "type": "string"
+        },
+        "circulating_market_cap": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The circulating market cap, if available.",
+          "title": "Circulating Market Cap"
+        },
+        "exchange_rate": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The current exchange rate, if available.",
+          "title": "Exchange Rate"
+        },
+        "is_smart_contract_verified": {
+          "description": "Indicates if the token's contract is verified.",
+          "title": "Is Smart Contract Verified",
+          "type": "boolean"
+        },
+        "is_verified_via_admin_panel": {
+          "description": "Indicates if the token is verified by the Blockscout team.",
+          "title": "Is Verified Via Admin Panel",
+          "type": "boolean"
+        },
+        "name": {
+          "description": "The full name of the token (e.g., 'USD Coin').",
+          "title": "Name",
+          "type": "string"
+        },
+        "symbol": {
+          "description": "The symbol of the token (e.g., 'USDC').",
+          "title": "Symbol",
+          "type": "string"
+        },
+        "token_type": {
+          "description": "The token standard (e.g., 'ERC-20').",
+          "title": "Token Type",
+          "type": "string"
+        },
+        "total_supply": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The total supply of the token.",
+          "title": "Total Supply"
+        }
+      },
+      "required": [
+        "address",
+        "name",
+        "symbol",
+        "token_type",
+        "total_supply",
+        "circulating_market_cap",
+        "exchange_rate",
+        "is_smart_contract_verified",
+        "is_verified_via_admin_panel"
+      ],
+      "title": "TokenSearchResult",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "content_text": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Optional human-readable summary used for MCP content responses.",
+      "title": "Content Text"
+    },
+    "data": {
+      "description": "The main data payload of the tool's response.",
+      "items": {
+        "$ref": "#/$defs/TokenSearchResult"
+      },
+      "title": "Data",
+      "type": "array"
+    },
+    "data_description": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "A list of notes explaining the structure, fields, or conventions of the 'data' payload.",
+      "title": "Data Description"
+    },
+    "instructions": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "A list of suggested follow-up actions or instructions for the LLM to plan its next steps.",
+      "title": "Instructions"
+    },
+    "notes": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "A list of important contextual notes, such as warnings about data truncation or data quality issues.",
+      "title": "Notes"
+    },
+    "pagination": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/PaginationInfo"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Pagination information, present only if the 'data' is a single page of a larger result set."
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "title": "ToolResponse[list[TokenSearchResult]]",
+  "type": "object"
+}

Changed6 schema fields changedMar 12, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / chain_id / title
```
Removed value: -"Chain Id"
```

changedInput schema / properties / symbol / description

Previous value: -"Token symbol or name to search for"New value: +"Token symbol or name to search"

removedInput schema / properties / symbol / title
```
Removed value: -"Symbol"
```

removedInput schema / title

Removed value: -"lookup_token_by_symbolArguments"

First observedJan 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint true, destructiveHint false), the description adds important behavioral details: matches are based on symbol/name similarity, multiple potential matches may be returned, and only the first 7 from the Blockscout API are included. This provides useful context about the fuzzy matching and result truncation 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 three concise sentences, each serving a purpose: what it does, the nature of results, and the limit. It is front-loaded with the action and contains no filler or repetition.

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?

Given the output schema and annotations, the description covers key contextual gaps: the fuzzy matching behavior and the 7-match limit. It does not explicitly state behavior for no matches, but that is likely covered by the output schema. Overall, it is sufficiently complete for a search tool with a structured response.

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 semantic value by explaining that the search uses 'symbol or token name similarity' and returns 'potential matches', indicating fuzzy matching rather than exact lookup. This goes beyond the schema's simple 'Token symbol or name to search for'.

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 'Search for token addresses by symbol or name' with a specific verb and resource, and clarifies it returns multiple potential matches. It is clearly distinguished from siblings like get_tokens_by_address by focusing on symbol/name lookup rather than address-based queries.

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?

The description clearly implies when to use this tool: when you need to find token addresses from a symbol or name. It notes that results are based on similarity and only the first 7 matches are returned, helping set expectations. However, it does not explicitly name alternatives or exclusions, though the purpose makes the use case obvious.

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

All blockscout-mcp-server 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.