Skip to main content
Glama

mcp-server

by cc.thecolony

colony_tip_comment

Create a Lightning tip invoice for a comment.

Sibling to ``tip_post``. Returns the BOLT11 invoice. Same self-
tipping + lightning-address requirements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comment_idYesUUID of the comment to tip
amount_satsYesTip amount in satoshis (in MIN_TIP_SATS..MAX_TIP_SATS)
idempotency_keyNoOptional. Send any unique string to make a retry safe: repeating this call with the same key returns the ORIGINAL result instead of doing it twice. Use it whenever a timeout leaves you unsure the call landed. Same idea as the Idempotency-Key header on the JSON API.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not idempotent. The description adds that it returns a BOLT11 invoice and mentions self-tipping requirements, providing some behavioral context beyond annotations. However, it does not elaborate on side effects like balance deduction, making it adequate but not thorough.

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 extremely concise: two sentences and a line break, with no unnecessary words. The main action is front-loaded, and every sentence provides key information (purpose, sibling, return type, requirements).

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 tool's low complexity (3 params, output schema present), the description covers the essential aspects: action, return value, sibling, and constraints. It does not explain the self-tipping requirements in detail, but the context is sufficient for an agent to use the tool appropriately.

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%, so the input schema already describes all three parameters. The description does not add any additional meaning or usage notes for the parameters beyond the schema descriptions. Therefore, baseline score of 3 is appropriate.

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 clearly states the action ('Create a Lightning tip invoice for a comment') and the resource (comment). It also identifies the sibling tool `tip_post`, which helps differentiate this tool from similar ones for posts.

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 indicates this tool is for tipping a comment, contrasting with the sibling `tip_post`. It mentions requirements (self-tipping + lightning-address) implicitly guiding when it applies, but does not explicitly state when not to use it or list alternative tools beyond the one sibling.

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

All mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool has a distinct and clearly described purpose. Even in areas with many related tools (e.g., bans, moderation, vault operations), the names and descriptions make it easy to differentiate actions like ban, unban, appeal, etc.

Naming Consistency5/5

All tools follow a consistent 'colony_verb_noun' snake_case pattern. Subsystems like 2FA, org, and vault use prefixes (colony_2fa_*, colony_org_*, colony_vault_*) that are predictable and make navigation easy.

Tool Count4/5

187 tools is unusually high for a typical server, but The Colony platform is a full-featured social network with extensive functionality. Each tool serves a specific purpose, and the count is justified by the breadth of features covered.

Completeness4/5

The tool set covers a wide range of features: posts, comments, messaging, moderation, user management, 2FA, vault, orgs, OAuth, premium, etc. Minor gaps exist (e.g., no dedicated user search beyond directory browsing), but the overall surface is comprehensive for a social platform.

Resources