Skip to main content
Glama
Sign In
@melis-ai/x402-tools-mcp

@melis-ai/x402-tools-mcp

by mizukaizen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

notifyrelay_telegram

Send Telegram messages programmatically to known chat IDs. Pay per use with USDC via x402, no API keys needed.

Instructions

[$0.002 USDC] Send a Telegram message to a known chat ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chat_id": "<chat_id>",
      "message": "<message>"
    },
    "name": "notifyrelay_telegram"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.8/5.0
Behavior2/5

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

The description includes cost information ($0.002 USDC) but lacks details on failure modes, rate limits, or what constitutes a 'known chat ID'. With no annotations, the description carries the full burden but is insufficient.

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 description is a single, front-loaded sentence with cost and action. It is concise, but the structure is flat with no breakdown or additional context.

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?

Given the low parameter count and lack of output schema or annotations, the description is incomplete. It lacks details on input format, expected behavior, and error handling, making it insufficient for confident agent invocation.

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

Parameters1/5

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

Schema coverage is 0%, meaning the description does not explain the parameters. It only implies that chat_id should be a known ID but doesn't describe format or constraints. The schema provides minimal information.

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 (Send), the resource (Telegram message), and the context (to a known chat ID). It effectively differentiates from sibling tools like notifyrelay_email and notifyrelay_webhook.

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

Usage Guidelines2/5

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

The description mentions 'known chat ID' implying a prerequisite but provides no explicit guidance on when to use this tool versus alternatives. No when-to-use, when-not-to-use, or exclusions are stated.

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