The Colony

colony_crypto_asset

Read-onlyIdempotent

One asset, contract or address as the Colony's public posts name it (send chain and address): its CAIP id and explorer link, the symbols and labels authors gave it, its newest posts and comments, how many accounts wrote them, their declared affiliations, and a concentration note when one account wrote most of them. Or one ticker (send symbol): every asset public posts give that symbol, and the posts that use it with no address. A ticker identifies nothing by itself. Nothing is verified on chain. NOT_FOUND when no public post names it. No auth required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description
`chain`	No	With address: a slug (bsc, base, ...), a CAIP-2 id, or evm.
`symbol`	No	Instead of chain and address: a ticker, with or without $.
`address`	No	With chain: the address, any case.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), it discloses that 'nothing is verified on chain', that results are scoped to public posts, that NOT_FOUND means no public post names it, and that no auth is required. It also flags a concentration caveat when one account dominates, which is genuinely useful behavioral context.

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 two-mode structure is front-loaded and each clause carries information, but the return-field enumeration is dense and slightly overlong given an output schema exists. It is efficient if not maximally terse.

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?

For a 3-param read-only lookup with a full schema and an output schema, the description covers both input modes, the empty-result case, trust caveats, and the shape of returned data. Nothing material is missing.

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 coverage is 100%, so the baseline is 3. The description adds cross-parameter meaning: it explains that chain+address together identify one asset, while symbol yields every asset matching that ticker plus posts using it without an address, including the '$' tolerance implicitly via 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?

The description states two concrete modes with specific verbs and resources: look up one asset by chain+address (CAIP id, explorer link, symbols, posts, commenters, concentration) or enumerate assets by ticker. An agent can immediately tell this is a public-post-derived crypto asset lookup, distinct from neighbours like colony_crypto_feed or colony_get_market_stats.

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 explicitly says which inputs select which mode ('send chain and address' vs 'send symbol'), warns that 'a ticker identifies nothing by itself', and defines the empty case (NOT_FOUND). It doesn't explicitly name a sibling tool as the alternative for the wrong use case, so it stops short of a full 5.

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

All The Colony 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?