Title95/100
Resolve Entity Slug
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Resolve an ambiguous entity name to its exact database slug. Call this FIRST when unsure about the exact identifier for a protocol, chain, token, or other entity. For protocols, returns both the sub-protocol slug and parent_protocol. Use parent_protocol with get_protocol_metrics (e.g., protocol="aave"), and slug for sub-protocol views. Many protocols have versions: aave → aave-v2, aave-v3 (sub-protocols), all under parent "aave". Examples: - resolve_entity({name: "aave"}) → finds sub-protocols (aave-v2, aave-v3) with parent_protocol="aave" and category - resolve_entity({name: "eth", entity_type: "token"}) → finds "coingecko:ethereum" - resolve_entity({name: "polygon", entity_type: "chain"}) → finds chain slug - resolve_entity({name: "lending", entity_type: "category"}) → finds exact category slug - resolve_entity({name: "usdt", entity_type: "stablecoin"}) → finds stablecoin with peg info - resolve_entity({name: "binance", entity_type: "cex"}) → finds the exchange name for get_cex_volumes Token matches are ranked by market cap, exact ticker first. Several tokens can share a ticker: check the name. Returns matches with slug, name, type, parent_protocol (for protocols), category, and confidence.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Input documentation gives an agent enough context to populate the arguments.
name
Name, ticker or partial slug to look up, for example "aave", "eth" or "polygon".
Clear enough to supply this argument.
entity_type
Narrows the search to one kind of entity, which helps when a name is shared (for example "polygon" is a chain and a token). When omitted, all kinds are searched.
Clear enough to supply this argument.
format
Use json when you need to read individual fields; csv is more compact and uses fewer tokens.
Clear enough to supply this argument.
Annotations100/100
All four behavior hints are declared.
{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}Output schema32/100
Declare the result fields and their types in the output schema.
View output schema
{
"type": "object",
"required": [
"metadata",
"data"
],
"properties": {
"data": {
"type": "array",
"items": {
"type": "object"
},
"description": "Result rows. Columns depend on the tool and its inputs; the text content holds the same rows."
},
"metadata": {
"type": "object",
"required": [
"row_count"
],
"properties": {
"notes": {
"type": "array",
"items": {
"type": "string"
},
"description": "How to read the rows: defaults or fallbacks the tool applied."
},
"warning": {
"type": "string",
"description": "Inputs that were skipped as invalid, with the closest valid names."
},
"row_count": {
"type": "integer",
"description": "Number of rows in data."
},
"sorted_by": {
"type": "string",
"description": "Sort applied to data."
},
"total_count": {
"type": "integer",
"description": "Number of matching rows before the limit, when known."
}
}
}
}
}