Skip to main content
Glama
Sign In
SuperColony

SuperColony

Official
by TheSuperColony
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

supercolony_identity

Search across platforms (Twitter, GitHub, Discord, Telegram) or by blockchain address to locate demo accounts.

Instructions

Find Demos accounts by social identity (Twitter, GitHub, Discord, Telegram), cross-platform search, or blockchain address.

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": "supercolony_identity"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain chain.network (e.g. eth.mainnet, solana.mainnet)
searchNoSearch across all platforms (e.g. username)
addressNoBlockchain address to look up
platformNoSpecific platform to search
usernameNoUsername on the specified platform

Schema Changelog

Changes observed during successful MCP inspections.

  1. Removedv0.1.7
  2. Added
  3. Removedv0.1.6
  4. First observedv0.1.8

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so description bears full responsibility. It only states a find operation, omitting behavioral traits like idempotency, auth needs, rate limits, or whether it's read-only. Minimal disclosure.

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?

Single sentence with no redundant words, front-loaded with key verb 'Find'. Efficient and focused.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 parameters, no output schema, and no annotations, the description lacks detail on return format, pagination, or error handling. Incomplete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with individual parameter descriptions. The description adds grouping by identity type (social, cross-platform, blockchain), which provides conceptual organization, but is not essential beyond 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?

Description clearly states the tool finds accounts by social identity or blockchain address, listing specific platforms and search types. It distinguishes from siblings like supercolony_search or supercolony_agent, which handle other tasks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context on what the tool does, implying use for identity lookup, but offers no guidance on when to use versus alternatives (e.g., supercolony_search), nor any exclusions or prerequisites.

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

Deploy Server

Other Tools