Skip to main content
Glama
Sign In
telegraph-mcp

telegraph-mcp

Official
by telegraphprotocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Deposit to escrow

telegraph_deposit

Deposit USDC from the server wallet into Telegraph escrow by approving and calling depositUSDC on chain; escrow funds pay for asks. Confirm the amount first and keep ETH for gas.

Instructions

Move USDC from this server's wallet into its Telegraph escrow balance (approve, then depositUSDC on chain; needs a little ETH for gas). Escrow then pays for asks. Confirm the amount with the user first. Withdrawing is explained in telegraph_docs topic payments.

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": {
      "amount_usd": "<amount_usd>"
    },
    "name": "telegraph_deposit"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_usdYesUSDC to deposit, e.g. 1 or 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations mark this as a non-read-only, non-idempotent, open-world operation; the description adds real value beyond them by naming the on-chain mechanism (approve, then depositUSDC), the gas requirement ('needs a little ETH'), and the user-confirmation rule. It stops short of warning that repeated calls deposit again (consistent with idempotentHint=false), which would have been the final piece.

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?

Three short sentences, front-loaded with the action and followed by the mechanism, the safety instruction, and the pointer to docs. Every sentence carries distinct information with no filler.

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?

For a one-parameter funding tool with annotations and no output schema, this covers what it does, how it executes, the gas prerequisite, and where to learn about the reverse operation. Only a pointer to verifying the resulting escrow balance (e.g., via telegraph_account) is missing.

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% and the single parameter's unit (USDC), bounds, and example are already documented in the schema. The description adds no format or deadline details, so the baseline 3 applies. The schema's 10,000 maximum is not echoed, but it is visible in 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?

States a specific verb and resource: 'Move USDC from this server's wallet into its Telegraph escrow balance.' The direction of funds is unambiguous, and the tool is clearly distinguishable from siblings like telegraph_account or telegraph_docs.

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?

Explains the downstream purpose ('Escrow then pays for asks') so the agent knows why to call it, and adds a mandatory precondition ('Confirm the amount with the user first'). It routes the inverse operation elsewhere ('Withdrawing is explained in telegraph_docs topic payments') but does not state conditions when depositing is unnecessary.

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